22 Jan
2019
22 Jan
'19
11:02 a.m.
Hi all, Some of you have probably noticed that Jenkins was not responsive this morning. As a result, we've had to restart it. The service is up and running and everything should be back to normal by now. If you've had any running jobs by the time of the restart, please re-trigger them by going to your patch in Gerrit or PR in GitHub and comment '*ci test please*' to make sure that the CI system will test your jobs. Sorry for any inconvenience that was caused and do not hesitate to reach out to me or anyone from the CI team with questions or requests for assistance. Thanks, -- DANIEL BELENKY