Hi, I think you can add "GERRIT_REFSPEC" parameter to this job (and all others needed parameters by your job) with a default value and it'll be overridden when triggered by a Gerrit event. But the GERRIT_REFSPEC parameter, and some others Gerrit's parameters will change on each changeset. Not sure that you really want this behaviour.
If your usecase is to rebuild a previous build, you can use the "Retrigger" button on the build page. Michaël Le mercredi 21 octobre 2015 15:12:32 UTC+2, John Mellor a écrit : > > I have a couple of prototype Gerrit integration builds up and running, > with some issues. All of the builds are freestyle projects, in case that > matters. > > > > One of the issues is that I do not seem to be able to kick off a build > manually because of the way that the sourcecode management has to be > configured. I have to use a repo Refspec of $GERRIT_REFSPEC, which is not > valid unless the build is triggered by the Gerrit plugin. > > > > For a build-now pushbutton build or a dependent build, how can I set this > value to some default that can be overloaded when triggered by Gerrit? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/55932274-c6d5-4aa2-99f7-2034605e5357%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
