<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div>Hello folks,<br><br></div>We'll have a Jenkins outage on 1st Nov for Jenkins. This outage will be from 0900 to 1700 UTC.<br><br></div>EDT: 0500 to 1300<br></div>CET: 1000 to 1800<br></div>IST: 1430 to 2230<br><br></div>Given that Michael and I are co-located and this is a holiday in India, it's a good opportunity for us to fix a lot of security issues with the old Jenkins server and move it onto a fresh and clean machine. At this point, we cannot estimate how much time we'll take.<br><br></div>Ideally, here's what we're looking to do:<br><br></div>* Setup a new VM for Jenkins in CentOS 7.<br></div>* Install Jenkins and dependencies.<br></div>* Move over the /var/lib/jenkins folder from current install to new one.</div><div>* Switch DNS for <a href="http://build.gluster.org">build.gluster.org</a> to the new server.<br></div>* Move over the <a href="http://bits.gluster.org">bits.gluster.org</a> data to a <a href="http://http.int.rht.gluster.org">http.int.rht.gluster.org</a> and setup a proxy redirect.<br></div>* Change the release job to push from Jenkins job to <a href="http://http.int.rht.gluster.org">http.int.rht.gluster.org</a>.</div><div>* Swtich DNS for <a href="http://bits.gluster.org">bits.gluster.org</a>.</div><div><br></div><div>Depending on complications that may arise during this time, we may or may not do the <a href="http://bits.gluster.org">bits.gluster.org</a> migration along with this.<br></div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><br>-- <br><div class="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>