THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Warning | ||
|---|---|---|
| ||
This page is obsolete and is no longer being updated. Please refer to the Contributing tab on http://trafodion.incubator.apache.org for information on how to contribute to Trafodion:
|
This page describes the contributor workflow for changes to Trafodion code and documentation. To contribute to the wiki, see Contribute to the Wiki.
...
Command-line instructions here assume you have "hub" installed. If you do not use "hub", you can accomplish the same thing using the github.com web site plus some git commands. You can alias "git" to "hub" for ease of use, but here we'll use "hub" explicitly for clarity. Instructions below use GHuser in place of your github username.
| Note |
|---|
Refer to Development Tools for information on how to set up your git environment. Refer to https://hub.github.com/ for information on how to install hub. |
Initial Steps (need not be repeated for subsequent changes)
Clone the
...
Trafodion Repository from the GitHub
...
Mirror
If you are using ssh:| Code Block | ||||
|---|---|---|---|---|
| ||||
git clone git@github.com:apache/incubator-trafodion |
...
OR
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
hub clone -p apache/incubator-trafodion |
...
## -p option for ssh |
Fork the
...
Repository on
...
- cd incubator-trafodion
Then:
- hub fork
OR
...
GitHub, If Needed
If you've never forked the repository on GitHub, then do the following.
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd incubator-trafodion
hub fork |
Alternative method.
- Use the Fork button on the web interface: https://github.com/apache/incubator-trafodion
...
Execute the following command: git remote add GHuser
...
git@github.com:GHuser/incubator-trafodion
Create a Task Branch
...
- git fetch --all
| Code Block | ||
|---|---|---|
| ||
# Ensure that you have the latest changes.
hub fetch --all
# Base your branch on the latest master.
hub checkpout -b <mybranch> orgin |
...
/master |
Make Changes
Once you have created your task branch, you are ready to make changes.
...
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 :
- The first two columns in build-job table are links to the specific sub-job, so you can drill down there.
- 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 :
- The location of the logfiles is much more predictable than it used to be.
- You can go to http://traf-logs.esgyn.com/PullReq/
- 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.
- 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
- If all is well, a committer will merge your change into the Apache repo, which is mirrored on github.
- You may be asked to close out the JIRA or other follow up.
- Yea! Thanks for your contribution to Trafodion.
...