Yes that support case is in the pipe. The pull request from Jesse from what I can see only fixes leaked project and build references. I doubt it would totally fix the start/stop issue. For example if someone would remove the trigger config from a job and post the change via cli the stop method would not be called and leave the old listener hanging and causing problems. So there are still things left to be fixed there.
/B On Tue, Sep 23, 2014 at 8:49 AM, James Nord (jnord) <[email protected]> wrote: > Most likely these are the links you are looking for > > > > https://issues.jenkins-ci.org/browse/JENKINS-23152 > > https://github.com/jenkinsci/gerrit-trigger-plugin/pull/154/ > > https://cloudbees.zendesk.com/requests/7459 > > > > /James > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Robert Sandell > *Sent:* 15 September 2014 12:25 > *To:* [email protected] > *Subject:* Re: gerrit-trigger plugin > > > > 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. > > -- > 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.
