RE: Jenkins maintenance - complete

[Steve Varnau <st...@esgyn.com>]

The new configuration has had successful check test. The only unintended
consequence is that the 4 open pull requests got an extra test-failed
message.  All clear -- feel free to update or add new pull requests.



Next test will be tonight’s daily build/test.



--Steve



*From:* Steve Varnau [mailto:steve.varnau@esgyn.com]
*Sent:* Monday, October 12, 2015 2:20 PM
*To:* 'dev@trafodion.incubator.apache.org' <
dev@trafodion.incubator.apache.org>
*Subject:* Jenkins maintenance



Hi all,



As I mentioned last week, I’m setting up Jenkins automation changes to
support multiple active branches. This will allow us to have a release
stable branch for fixes in addition to new development on master branch.



The changes are a bit involved, and may disrupt on-going test jobs, and
especially any new test jobs.  So I’d like to take some time this evening
to install and test out the changes.  You may want to hold off of
initiating or updating pull-requests starting about 7pm US Pacific time,
until I give the all-clear message to this list.



No worries if you start a job anyway. The worst that should happen is a
failed test-job that has to be re-run.



BTW, the new changes also have a fix for the problem that caused a number
of failures in today’s test runs. (A check build ran around the same time
as the daily tests were running, and the test jobs got confused and picked
up the check build instead of the daily build.)



--Steve