Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No way to access CASC_JENKINS_CONFIG or other configuration variables when running Jenkins as a Linux service on a VM
See original GitHub issueJenkins version: 2.150.1 Configuration as Code Plugin version: 1.4 OS: Centos 7.6.1810
When running Jenkins as a Linux service using service jenkins start, all environment variables including CASC_JENKINS_CONFIG are stripped away and the jenkins.yaml configuration file is not loaded.
This can be worked around by moving jenkins.yaml from its generic location to $JENKINS_ROOT/jenkins.yaml, but the problem remains for other CasC configuration accessed through environment variables, such as CASC_VAULT_FILE and other Vault-related values.
Could these config options be provided to Jenkins in another way, e.g. in a config file or by providing arguments to the Jenkins run command?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hopefully just a typo? 🤔 Should read
CASC_JENKINS_CONFIGIt is that repo for packaging, no one is working on it (outside of changes required for the release automation project)
But anyone who is on the core team can merge PRs