It is a difference in behavior of core: stop/start is only called when configured via the UI. Not when done via cli, http api or reload from disk, which is a big pain in the behind. Somewhere there is a Jira issue reported on this which I can't find at the moment.
/B On Wed, Sep 10, 2014 at 4:39 PM, Patrick Bruneton <[email protected]> wrote: > Hi, > > I am using Jenkins 1.567 and Gerrit Trigger plugin 2.12.0-beta-4. > I have noticed the following behavior that I don't understand: > > 1. If I change a job config through the web UI, then instances > of com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger > receive a stop() and then a start() notification. > > 2. If I do the same change to the job, but through the Jenkins CLI, then > GerritTrigger receive only a start(). No stop(). > > I expected the behavior from a plugin point of view to be the same in the > two cases. > Am I wrong ? > Could this be a bug in Gerrit Trigger plugin ? > > Patrick > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
