|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
This is related to JENKINS-23152 that I'm currently working on.
The issue is that Jenkins Job Builder is using http post of config.xml and in that scenario core isn't calling trigger.stop/start in the same way as when saving config via UI, or it's using CLI which behaves even worse, so the old configuration from the previous trigger config hangs around and the new one isn't activated correctly.