[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup

[email protected] (JIRA) Mon, 10 Jun 2019 08:40:07 -0700

Title: Message Title

Rudolf-Walter Kiss-Szakacs commented on

[Originally posted on the associated GitHub issue, replicating here for visibility.]

I have personally worked around this by applying CasC configs through a job, and disabling CasC for Jenkins startup by pointing it to an empty file.

That is, I have a job that does a SCM checkout, and then runs something like this as a system-groovy script (from the groovy plugin):

 
                                                                import jenkins.model.GlobalConfiguration
import io.jenkins.plugins.casc.ConfigurationAsCode
import io.jenkins.plugins.casc.CasCGlobalConfig
def workspacePath = build.environment.WORKSPACE
def jcascConfig = GlobalConfiguration.all().get(CasCGlobalConfig.class)
try {
	jcascConfig.setConfigurationPath(workspacePath)
	jcascConfig.save()
	ConfigurationAsCode.get().configure()
} finally {
	jcascConfig.setConfigurationPath("${workspacePath}/empty.yaml")
	jcascConfig.save()
}
 
                                                            

(Note that below CasC version 1.20, you need to have at least one setting in empty.yaml, a completely empty file generates a null pointer exception.)

Add Comment

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199824.1559748979000.24567.1560181200340%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup

Reply via email to