Page History

...

Normally, the Traf-Jenkins user will post a message in the pull-request with a link to the results. But you can check the Jenkins server to see the status even before the tests are finished. Look in the "Build History" table for the build/test job that matches your pull-request: . For instance master branch tests are at "https://jenkins.esgyn.com/job/Check-PR-master/"

One way to look at logs :

1. The first two columns in build-job table are links to the specific sub-job, so you can drill down there.
2. The console log of each job has a link to the log file directories (about 7 lines from close to the top). Look carefully for "Detailed logs".

Another way to look at logs :

1. The location of the logfiles is much more predictable than it used to be.
2. You can go to http://traf-logs.esgyn.com/PullReq/
3. Click on the number of the pull request, such as http://traf-logs.esgyn.com/PullReq/18/. The next directory level is the build number. With multiple commits or re-tests, it is possible for a pull request to have multiple builds.
4. Under that, there is a directory for each specific job, such as http://traf-logs.esgyn.com/PullReq/18/35/regress-seabase-ahw2.2/

The check tests do not include all of the automated daily tests. If you (or another contributor) want, you can run additional tests on the pull request.

More information about the automated test set-up.

Merge changes

1. If all is well, a committer will merge your change into the Apache repo, which is mirrored on github.
2. You may be asked to close out the JIRA or other follow up.
3. Yea! Thanks for your contribution to Trafodion.

...