[Gluster-Maintainers] Automatic triggering broken on Jenkins

Kaushal M kshlmster at gmail.com
Thu Nov 19 11:14:59 UTC 2015

On Thu, Nov 19, 2015 at 4:34 PM, Niels de Vos <ndevos at redhat.com> wrote:
> On Thu, Nov 19, 2015 at 03:54:54PM +0530, Kaushal M wrote:
>> The gerrit-trigger plugin which automatically triggered jobs is
>> temporarily not working. We are trying to find out why and will fix it
>> soon.
>> In the mean time maintainers who need tests to run immediately, can
>> manually trigger jobs. To manually trigger jobs,
>> 1. Get the REFSPEC of the change from Gerrit. This will be available
>> from the review page for a change, and will be in the format
>> `refs/changes/42/11342/10`. You can get it easily from the `Download`
>> menu in the top-right of the page.
>> 2. Go to the job page for the test you want on jenkins and click on
>> `Build with parameters`. You should land up on a page with URL similar
>> to `https://build.gluster.org/job/rackspace-regression-2GB-triggered/build?delay=0sec`
>> 3. Enter the REFSPEC for the change in to the box and click build.
>> Jenkins should now schedule, run and report back the job status to
>> gerrit.
> Here is an alternative to run all tests, and not only the regression
> test.
> 1. open https://build.gluster.org/gerrit_manual_trigger/
> 2. in the search field, enter: status:open change:12345
> 3. click "Search"
> 4. select the change that needs testing
> 5. click "Trigger Selected"

This is a much better solution. Thanks Neils.

> HTH,
> Niels

More information about the maintainers mailing list