[JIRA] [core] (JENKINS-30376) More equals methods on Jenkins runtime objects

[sam.mxra...@gmail.com (JIRA)]

Title: Message Title

Sam Gleske commented on JENKINS-30376   Re: More equals methods on Jenkins runtime objects Version controlling the job configs means that you must modify the XML (not recommended) and reload the Jenkins master configuration. In the pull request I linked, I've explicitly given an example where it is a use case (currently being used in production). Here's the example, which could have been viewed by clicking the link in the original description. import hudson.security.SecurityRealm import org.jenkinsci.plugins.GithubSecurityRealm String githubWebUri = 'https://github.com' String githubApiUri = 'https://api.github.com' String clientID = 'someid' String clientSecret = 'somesecret' String oauthScopes = 'read:org' SecurityRealm github_realm = new GithubSecurityRealm(githubWebUri, githubApiUri, clientID, clientSecret, oauthScopes) //check for equality, no need to modify the runtime if no settings changed if(!github_realm.equals(Jenkins.instance.getSecurityRealm())) { Jenkins.instance.setSecurityRealm(github_realm) Jenkins.instance.save() } That would be executed on the script console. Notice that the GithubSecurityRealm class has an equals method implemented. It is being used by github_realm.equals(Jenkins.instance.getSecurityRealm()) Or you could save it as a groovy script (e.g. security-realm.groovy). Then once you have the script config management would essentially execute the following command. curl --user "userName:apiToken" --data-urlencode "script=$(<./security-realm.groovy)" http://localhost:8080/scriptText Basically, I've decided if you need to log into the web UI and click a check box to configure in production then you've failed. Configuration management needs to maintain the entire state of the system. By having configuration management manipulate the Jenkins runtime via the Script Console this is easily accomplished (with a token that has administer permissions). This is the better way to do it rather than maintain the XML on the filesystem. By modifying the runtime via the script console you're modifying the configuration itself. By executing Jenkins.instance.save() you're serializing the runtime to XML and saving the configuration to disk. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.