On Mon, Jan 4, 2016 at 4:58 PM, Niels de Vos <[email protected]> wrote: > On Wed, Dec 30, 2015 at 11:47:14AM +0100, Niels de Vos wrote: >> Jenkins is not triggering smoke and regression tests at the moment. I >> have triggered smoke and regression tests for many patch sets manually >> through: >> >> 1. open https://build.gluster.org/gerrit_manual_trigger/ >> 2. search: "status:open after:2015-12-27 label:Verified=0 NOT >> label:Code-Review=-1" >> 3. select all changes >> 4. click "trigger selected" >> >> Could someone look into getting the connection between Jenkins and >> Gerrit up again? >> >> Thanks, >> Niels > > This does not seem to have been resolved yet. I've executed the above > procedure again. Many regression tests have been scheduled now. > > Niels >
I've scheduled a Jenkins restart, which should fix the connection. I've also aborted the following hung netbsd regression runs, they can be retriggered after Jenkins restarts. https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13124/ https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13126/ https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13130/ https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/13132/ ~kaushal > _______________________________________________ > Gluster-infra mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-infra _______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
