No worries. Glad a quick googling of stack overflow saved the day (as it often does). :D
On Thu, Aug 30, 2018 at 5:13 PM Frederic Gurr < [email protected]> wrote: > Hi Nick, > > Thanks for the suggestions and finding the fix! > > I'll keep the old Gerrit triggered job around for a few days before I > retire it. > > > Regards, > > Fred > > On 30.08.2018 18:49, Nick Boldt wrote: > > OK, ignore all those suggestions. > > > > Here's the real reason: https://stackoverflow.com/a/11525496/1661797 > > > > https://git.eclipse.org/r/#/c/128383/ > > --> > https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/8/ > > --> it's running! > > > > And yes, you can have two builds for the same gerrit trigger... as we > > see here: > > > > image.png > > > > > > > > On Thu, Aug 30, 2018 at 12:41 PM Nick Boldt <[email protected] > > <mailto:[email protected]>> wrote: > > > > Four ideas for why it's not triggering: > > > > a) you have BOTH "Gerrit event" and "Build periodically" as Build > > Triggers enabled. Can both actually run when there's no gerrit info > > provided because you're doing a crontab-triggered build? I guess so > > if it's building a sanity-check build every monday, so maybe this > > isn't an issue. But surely you'd rather have a non-gerrit, > > just-build-latest-in-master job run on Mondays instead? > > > > b) "Strategy for choosing what to build" - maybe that's not needed > > or conflicts w/ the other Gerrit Trigger info? > > > > c) there's already another gerrit-listening job enabled [1] for the > > repo, so maybe only the old is being fired. If the old one is > > disabled/deleted, maybe the new one will fire instead? > > > > d) Or is there some sort of api/ssh key, handshake, etc. needed to > > configure your gerrit w/ the job? Does the job need to have > > permissions/ACL set up so that gerrit can trigger it? > > > > [1] > https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/ > > > > > > > > > > -- > > > > Nick Boldt > > > > Principal Software Engineer, RHCSA > > > > Productization Lead :: JBoss Tools & Dev Studio > > > > IM: @nickboldt / @nboldt / http://nick.divbyzero.com > > > > <https://red.ht/sig> > > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > > > @ @redhatnews <https://twitter.com/redhatnews> Red Hat > > <https://www.facebook.com/RedHatInc> > > <https://www.facebook.com/RedHatInc> > > > > > > “The Only Thing That Is Constant Is Change” - Heraclitus > > > > > > _______________________________________________ > > cross-project-issues-dev mailing list > > [email protected] > > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > -- > Frederic Gurr > Release Engineer | Eclipse Foundation Europe GmbH > > Annastr. 44, D-64673 Zwingenberg > Handelsregister: Darmstadt HRB 92821 > Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Nick Boldt Principal Software Engineer, RHCSA Productization Lead :: JBoss Tools & Dev Studio IM: @nickboldt / @nboldt / http://nick.divbyzero.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @ @redhatnews <https://twitter.com/redhatnews> Red Hat <https://www.facebook.com/RedHatInc> <https://www.facebook.com/RedHatInc> “The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
