Hello,
I had to do an unplanned Jenkins restart. Jenkins was not responding to any
of the requests and was not giving back the regression votes.
I did update the vote verified values of regression jobs which seemed to
change to 0 all of a sudden and was not giving back the vote. I'm
investigating
Oops, big note: Centos Regression jobs may have ended up canceled. Please
retry them.
On Fri, Aug 24, 2018 at 9:31 PM Nigel Babu wrote:
> Hello,
>
> We've had to do an unplanned Jenkins restart. Jenkins was overloaded and
> not responding to any requests. There was a backlog of over 100 jobs as
Hello,
We've had to do an unplanned Jenkins restart. Jenkins was overloaded and
not responding to any requests. There was a backlog of over 100 jobs as
well. The restart seems to have fixed things up.
More details in bug: https://bugzilla.redhat.com/show_bug.cgi?id=1622173
--
nigelb
Hello folks,
I've just restarted Jenkins for an security update to a plugin. There was
one running centos-regression job that I had to cancel.
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
Le lundi 20 novembre 2017 à 12:28 +0530, Nigel Babu a écrit :
> I noticed that Jenkins wasn't loading up this morning. Further
> debugging
> showed a java heap size problem. I tried to debug it, but eventually
> just
> restarted Jenkins. This means any running job or any job triggered
> was
>
I noticed that Jenkins wasn't loading up this morning. Further debugging
showed a java heap size problem. I tried to debug it, but eventually just
restarted Jenkins. This means any running job or any job triggered was
stopped. Please re-trigger your jobs.
--
nigelb
Hello folks,
I had to do a quick Jenkins upgrade and restart this morning for an urgent
security fix. A few of our periodic jobs were cancelled, I'll re-trigger
them now.
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
