Trafodion Developers,
One more change in the check & gate testing for trafodion/core repo. At the
request of the SQL team leads, the core-regress-seabase suite has been added.
This previously ran only nightly, but will now be run for each submitted
change. This change is now implemented.
The other part of the request is to run the core-regress-* suites on release
build flavor instead of debug flavor, which should speed things up. That change
depends on another infrastructure change, but is coming soon.
-Steve
Trafodion Infra
_____________________________________________
From: Varnau, Steve (Trafodion)
Sent: Monday, August 11, 2014 11:19
To: [email protected]
Subject: New Build-check test for core and dcs
Trafodion Developers,
FYI.
You may have noticed that starting last week a new test job has been
running on every check and gate test for core repo. It runs in parallel and
faster than other jobs, so it should not normally slow anything down.
After running successfully for a few days, it has now been made a voting
test, meaning it could cause your change to fail. I wanted to let you know what
things it is checking.
The job exercises packaging build targets that other jobs don't, in order
to catch any makefile issues before they impact the daily build. For the same
reason, it uses the opposite build flavor (release) than test jobs that use
debug flavor.
Finally, there is a post-build check script that checks:
1) if any versioned files have been modified in the build.
2) if any new untracked files have been created in the build.
This is to ensure that .gitignore files are maintained. If you add new
build output that are not covered by existing .gitignore rules, you'll need to
update them. See "git help ignore".
For the DCS repo, this check script has also been added to the existing
dcs-build job.
-Steve
--
Mailing list: https://launchpad.net/~trafodion-development
Post to : [email protected]
Unsubscribe : https://launchpad.net/~trafodion-development
More help : https://help.launchpad.net/ListHelp
