Jenkins Gerrit Trigger does not work with new DRAFT->PUBLISH transition in Gerrit 2.3?

[Mateusz Grzechociński]

Hi,

I've just switched to Gerrit v2.3. Unfortunately, when I'm trying to push my change to refs/drafts/* and then I click 'Publish' - Jenkins Gerrit Trigger does not discover that change and does not force Jenkins to rebuild this change 

Any new configuration is needed? In v2.2.2.1 when pushed into refs/for/* everything worked fine.

Matthew

[Roland Schulz]

Hi,

I opened a bug for that https://issues.jenkins-ci.org/browse/JENKINS-13403 . I think it is a problem with the Jenkins plugin not with Gerrit itself.

Roland

2012/4/13 Mateusz Grzechociński <mateusz.gr...@gmail.com>

--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

--
ORNL/UT Center for Molecular Biophysics cmb.ornl.gov
865-241-1537, ORNL PO BOX 2008 MS6309

[David Pursehouse]

Hi,

I opened a bug for that https://issues.jenkins-ci.org/browse/JENKINS-13403 . I think it is a problem with the Jenkins plugin not with Gerrit itself.

This is not a bug in the plugin.  It's because the Jenkins user cannot see the `patchset-created` event (it's visible only to the change owner) and there is no publicly visible event sent when the change is published (moved from DRAFT to NEW status).

I've filed a bug report [1] and I have a patch on Gerrit that fixes it.  It'll get uploaded to gerrit-review later (hopefully today) after passing internal review.

[1] http://code.google.com/p/gerrit/issues/detail?id=1437

--
David Pursehouse
Configuration Manager
Sony Mobile Communications Japan, Inc