Christian submitted a pull request that fix the reload problem(https://github.com/jenkinsci/gerrit-trigger-plugin/pull/77), rename through Jenkins still work but the only case still not working is when you rename on disk then reload the configurations, which I am not sure is a really common use case because you not to update all the jobs that call the renamed job.
To fix the problem properly, we would need the Trigger.stop to get called when reloading the configurations or an event when reloading the configurations so we could remove the all the GerritTriggers but both are not currently working/available. So far, I do not see a way we could fix the last use case. On Wednesday, September 18, 2013 3:56:33 AM UTC-4, Robert Sandell wrote: > > We used to have the project name as the hashKey for the listener list as a > previous fix for the reload from disk problem, but that caused a bug when > the project was renamed see [1]. > > I guess the bug fix for project renamed caused the reload from disk to > reappear. > > Whatever the reload from disk fix will be it also needs to address project > renames. > > > > > https://github.com/jenkinsci/gerrit-trigger-plugin/commit/4cbed3ca42f7cdc3444a6e8ceb434bbd58362afb > > > > * * > > *Robert Sandell* > > Software Tools Engineer - SW Environment and Product Configuration > > Sony Mobile Communications > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Hugo Arès > *Sent:* den 17 september 2013 16:14 > *To:* [email protected] <javascript:> > *Subject:* Re: implementation of equals and hashcode method in > AbstractItem ? > > > > > > Your comment about not storing the abstractProject sounds correct to me. > > > > GerritTrigger extend Trigger and Trigger is storing the job also > (gerritTrigger have its own reference but do not need to). > > > I am looking at how I could fix this without comparing job, here is more > info on the problem: > > -Trigger start gets called when loaded in memory so a gerrit listener is > created > -Reload configuration happens but Trigger stop is not called (as it is > when a job configuration change) which would remove the gerrit listener. > -Trigger start gets called and we end up with a second listener. > > I could add validation in the gerritTrigger start to make sure we remove > old listener for the same job name but before I go this way, is the stop > method supposed to be called when reloading the configurations? > > -- > 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] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/groups/opt_out.
