Re: Update jobs via Script Console does not take effect

2015-09-25 Thread Sverre Moe
I have added stopping the old trigger and starting the new trigger. I have also a solution that worked without this: def jenkinsInstance = jenkins.model.Jenkins.getInstance() def SCM_TRIGGER_DESCRIPTOR = jenkinsInstance.getDescriptorOrDie(SCMTrigger. class) def developmentView = jenkinsInstance

Re: Update jobs via Script Console does not take effect

2015-09-21 Thread Daniel Beck
You forgot to `start(Job, boolean)` the trigger you added. You'll probably also need to `stop()` any existing SCMTrigger that gets replaced by yours. On 21.09.2015, at 16:11, Sverre Moe wrote: > It seems when I updated a Job configuration with Groovy in the Script console > it didn't really ta

Update jobs via Script Console does not take effect

2015-09-21 Thread Sverre Moe
It seems when I updated a Job configuration with Groovy in the Script console it didn't really take effect. def jenkinsInstance = jenkins.model.Jenkins.getInstance() def developmentView = jenkinsInstance.getView("Development") developmentView.getItems().each { project -> def trigger = new hud