----- Original Message ----- > From: "Barak Korren" <[email protected]> > To: "Vojtech Szocs" <[email protected]> > Cc: "Eyal Edri" <[email protected]>, "infra" <[email protected]> > Sent: Thursday, December 15, 2016 5:45:54 PM > Subject: Re: Ability to run [job-name] when a tag is pushed to Gerrit > > On 14 December 2016 at 19:18, Vojtech Szocs <[email protected]> wrote: > > > > If I'm reading [a] correctly, Jenkins Gerrit trigger (Jenkins plugin) > > doesn't explicitly support "tag pushed" event, which is strange (?), > > there is only "Ref Updated" which should include tag pushes. > > Its not the Gerrit trigger that is at fault here, its just the way the > event that Gerrit sends looks like. Which is to mean, Gerrit doesn't > have a specific event for tags.
Right, Jenkins Gerrit trigger just listens to events published through Gerrit's event stream. > > > So if it's not very feasible to implement e.g. "on-tag-push" trigger, > > I'm OK with [2] - posting Gerrit comment on (already merged & tagged) > > patch to re-trigger the build-artifacts job. > > Well, it may be feasible, but we don`t have any pre-existing > experience doing that, so it'll take some trial and error to get done > right, and perhaps some limitations may need to be in place (For > example, on the format that tag string can have, so we can > differentiate if from branches). Ideally, one could specify tag name prefix in Jenkins job YAML :-) Also, found this: http://stackoverflow.com/a/21605984 I'm also OK with what Eyal proposed: manually triggering the build job [build-artifacts] by posting a comment on Gerrit web. > > > -- > Barak Korren > [email protected] > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ > _______________________________________________ Infra mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/infra
