Page History

...

1. Follow the github conversation on your pull request and respond to questions and issues. You should be automatically subscribed to your own pull requests.
   • To make additional changes, go to your local working branch and make additional commits. Do NOT use --amend.
   • git checkout MyBranch ; <edits, etc> ; git commit
2. Push the branch to your github fork. These changes automatically show up in the pull-request.
   • git push GHuser  MyBranch

...

Checking Test Results

Automated tests take at least a couple hours from when your pull-request was okay'd by a project member or updated with a new commit.

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 for the build/test job that matches your pull-request: 

"https://jenkins02.trafodion.org/job/Check-PR/"

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 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://logs.trafodion.org/PullReq/
3. Click on the number of the pull request, such as http://logs.trafodion.org/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://logs.trafodion.org/PullReq/18/35/regress-seabase-ahw2.2/

Change Merged

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.

Related articles

...