I need to be able to load jenkins.yml from an URI
See original GitHub issueApparently we can’t load the jenkins.yml
from an URI anymore which is what I need at the moment to get it from a repository.
Alternatively I accept git repository polling if that is better to implement.
Once we could point CASC_JENKINS_CONFIG
to for example raw.github.com something.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Initial Settings - Jenkins
There are some configuration values that can only be modified while Jenkins is starting. This section describes those settings and how you can...
Read more >Getting started with Jenkins Configuration as Code - Eficode
Head over to the Plugin Manager under Manage Jenkins to install the Configuration as Code and configuration-as-code-support plugins. You'll find ...
Read more >jcasc - How to use a GitLab link for applying jenkins.yml file for ...
According to the problem description, an usage of pipelines may better suite what do you want to achieve. But you would need probably...
Read more >Getting started with Jenkins Configuration as Code
Create a multibranch pipeline using JCasC and Script ... You can save the file as casc.yml and push it to a URL where...
Read more >How To Automate Jenkins Setup with Docker ... - DigitalOcean
To use JCasC, you need to install the Configuration as Code plugin. Currently, no plugins are installed. You can confirm this by navigating...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@daniel-beck Point taken. I must admit i did this in a rush to get a use case we could demonstrate to a potential customer as having to mount in a file to a docker container to read it was a blocker for us. As such we bypassed the usual process.
In retrospective it wasn’t a good idea and we’ll avoid doing it in the future, and looking at the line you pointed to, i can already see what should be changed, while looking back at our previous discussions. 😃
Our focus for the next few weeks will be to create demo setup, with seed jobs, pipelines and a few key plugins configured, so we can showcase c-as-c to potential users of this plugin and continue improving the existing documentation.
we had a discussion about it today - sometimes it seems that PR is just to much overhead but as we can see you never know… lesson learned!