You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by Steve Varnau <st...@esgyn.com> on 2015/12/17 00:32:03 UTC
Trafodion Jenkins Downtime
Trafodion Developers,
Our automated test infrastructure is currently hosted on a public cloud
provider who is pulling the plug at the end of January. So I’ll be
migrating it to AWS. I’d like to schedule downtime for the jenkins server
on Monday January 4th for the transition.
Approx downtime: January 4th 10am-1pm PST, (6pm-9pm UTC).
Details:
· The new server will retain the same URL (jenkins.esgyn.com), so
it may take some time for the DNS update to propagate.
· Other than that, the downtime should not take long if all goes
well.
· Any current test job info will be transferred, so it will be
available from new server.
· The automation that interacts with github will need to be tested
out immediately after the transition. There may be a few spurious messages
/ test failures on open pull requests at that time. So you might want to *hold
off on making new pull requests at the beginning of January*.
· As for daily builds and test logs, those will start showing up at
slightly different URLs in January, and the old server will be shut down
after the old info ages off.
Questions? Concerns?
--Steve
RE: Trafodion Jenkins Downtime
Posted by Steve Varnau <st...@esgyn.com>.
The migration is completed and jobs are running.
There may be a period of instability in the new test environment. I’ll be
keeping an eye on things, and tonight’s build and full test run will be an
interesting check. Testing before the holidays seemed to be working well,
but I’m seeing that sometimes Hadoop is not coming up on some new VM
instances.
--Steve
*From:* Steve Varnau [mailto:steve.varnau@esgyn.com]
*Sent:* Sunday, January 3, 2016 4:06 PM
*To:* 'dev@trafodion.incubator.apache.org' <
dev@trafodion.incubator.apache.org>
*Subject:* RE: Trafodion Jenkins Downtime
Reminder that Jenkins testing will be down tomorrow morning (U.S. Pacific
time), and should be back up in the afternoon.
--Steve
*From:* Steve Varnau [mailto:steve.varnau@esgyn.com <st...@esgyn.com>]
*Sent:* Wednesday, December 16, 2015 3:32 PM
*To:* 'dev@trafodion.incubator.apache.org' <
dev@trafodion.incubator.apache.org>
*Subject:* Trafodion Jenkins Downtime
Trafodion Developers,
Our automated test infrastructure is currently hosted on a public cloud
provider who is pulling the plug at the end of January. So I’ll be
migrating it to AWS. I’d like to schedule downtime for the jenkins server
on Monday January 4th for the transition.
Approx downtime: January 4th 10am-1pm PST, (6pm-9pm UTC).
Details:
· The new server will retain the same URL (jenkins.esgyn.com), so
it may take some time for the DNS update to propagate.
· Other than that, the downtime should not take long if all goes
well.
· Any current test job info will be transferred, so it will be
available from new server.
· The automation that interacts with github will need to be tested
out immediately after the transition. There may be a few spurious messages
/ test failures on open pull requests at that time. So you might want to *hold
off on making new pull requests at the beginning of January*.
· As for daily builds and test logs, those will start showing up at
slightly different URLs in January, and the old server will be shut down
after the old info ages off.
Questions? Concerns?
--Steve
RE: Trafodion Jenkins Downtime
Posted by Steve Varnau <st...@esgyn.com>.
Reminder that Jenkins testing will be down tomorrow morning (U.S. Pacific
time), and should be back up in the afternoon.
--Steve
*From:* Steve Varnau [mailto:steve.varnau@esgyn.com]
*Sent:* Wednesday, December 16, 2015 3:32 PM
*To:* 'dev@trafodion.incubator.apache.org' <
dev@trafodion.incubator.apache.org>
*Subject:* Trafodion Jenkins Downtime
Trafodion Developers,
Our automated test infrastructure is currently hosted on a public cloud
provider who is pulling the plug at the end of January. So I’ll be
migrating it to AWS. I’d like to schedule downtime for the jenkins server
on Monday January 4th for the transition.
Approx downtime: January 4th 10am-1pm PST, (6pm-9pm UTC).
Details:
· The new server will retain the same URL (jenkins.esgyn.com), so
it may take some time for the DNS update to propagate.
· Other than that, the downtime should not take long if all goes
well.
· Any current test job info will be transferred, so it will be
available from new server.
· The automation that interacts with github will need to be tested
out immediately after the transition. There may be a few spurious messages
/ test failures on open pull requests at that time. So you might want to *hold
off on making new pull requests at the beginning of January*.
· As for daily builds and test logs, those will start showing up at
slightly different URLs in January, and the old server will be shut down
after the old info ages off.
Questions? Concerns?
--Steve