Below you'll find a list of the contributors, who have gone the extra mile and registered their iCLA. These recognised contributors have gained privileges in the project.
Name | Location | Email Address | Affiliation | iCLA Filed | JIRA | Confluence | Apache ID | Committer | IPMC/PPMC/PMC |
---|---|---|---|---|---|---|---|
Birdsall, Dave | Santa Clara, CA, USA | dave dot birdsall at esgyn dot com | Esgyn | 2015-06-01 | DaveBirdsall | dbirdsall | dbirdsall | 2015-06-01 | |
Broeder, Sean | sean dot broeder at esgyn dot com | Esgyn | sbroeder | | | ||||
Brown, Matt | matt dot brown at hp dot com | Hewlett Packard | | | mattbrown | 2015-05-26 | |||
Bucaojit, Oliver | oliver dot bucaojit at esgyn dot com | Esgyn | 2015-07-10 | obucaojit | oliver.bucaojit | | |||
Chen, Alice | alice dot chen at hp dot com | Hewlett Packard | | | alchen | 2015-05-26 | |||
Chen, Qifan | qifan dot chen at esgyn dot com | Esgyn | qfc | | | ||||
Deyager, Kevin | keving dot deyager at hp dot com | Esgyn | | | | ||||
Felici, Maurizio | maurizio dot felici at hp dot com | HP | |||||
Govindarajan, Selva | selva dot govindararajan at esgyn dot com | Esgyn | 2015-07-12 | selvag | | | |||
Hedge, Anuradha | anuradha dot hegde at esgyn dot com | Esgyn | hegdean | | | ||||
Jain, Rohit | rohit dot jain at hp dot com | Esgyn | | | | ||||
Li, Haifeng | haifeng dot li at adp dot com | ADP | haifengl | | | ||||
Markt, Dennis | dmarkt7370 at gmail dot com | Esgyn | 2015-07-12 | dmarkt | dmarkt | | |||
Marton, Roberta S. | roberta dot marton at esgyn dot com | Esgyn | | | | 2015-06-04 | |||
Moran, Amanda | San Jose, CA, USA | amanda dot kay dot moran at gmail dot com | Esgyn | amoran | amoran | amanda | 2015-06-01 | ||
Muthuswamy, Venkat | venkat dot muthuswamy at esgyn dot com | Esgyn | 2015-07-14 | venkatmu | venkat1m | | |||
Owhadi, Eric | eric.owhadi@esgyn.com | Esgyn | 2015-07-14 | eowhadi | eowhadi | eowhadi | |||
Qin, Howard | Shanghai, China | hao dot qin at hp dot com | HP | howard | | | |||
Pearson, Carol | carol dot pearson234 at gmail dot com | Esgyn | 2015-07-10 | carolp222 | carolp222 | | |||
Sadashiva, Aruna | San Jose, CA, USA | aruna dot sadashiva at hp dot com | HP | saruna | | | |||
Shaposhnik, Roman | roman at shaposhnik dot com | | | rvs | |||||
Sharma, Anoop | San Jose, CA, USA | anoop dot sharma at esgyn dot com | Esgyn | anoopsharma | | | |||
Smits, Pierre | The Netherlands | pierre dot smits at gmail dot com | 2014-10-13 | pfm.smits | | pierresmits | |||
Stack, Michael | stack at duboce dot net | | | stack | |||||
Subbiah, Suresh | Dallas, TX. USA | suresh dot subbiah60 at gmail dot com | Esgyn | 2015-05-27 | suresh_subbiah |suresh_subbiah | sureshs | 2015-06-07 | |
Tapper, Gunnar | gunnar dot tapper at esgyn dot com | Esgyn | 2015-07-15 | gtapper | gtapper | | |||
Varnau, Steve | Bay Area, CA, USA | steve dot varnau at esgyn dot com | Esgyn | 2015-07-10 | steve.varnau | steve.varnau | svarnau | 2015-08-19 | |
Vasudev, Prashanth | prashanth dot vasudev at esgyn dot com | Esgyn | 2015-07-15 | vasudevp | vasudevp | | |||
Xu, Weiqing | Shanghai, China | xuweiqingchn at gmail dot com | HP | weiqing | | | |||
Zeller, Hans | hans dot zeller at esgyn dot com | Esgyn | 2015-07-13 | hzeller | hans.zeller | | |||
Zuo, RuoYu | Shanghai, China | joshuamurdoc at gmail dot com | HP | 2015-07-17 |
Incubation Mentors
Name | Email Address | ||
---|---|---|---|
Das, Deverai | ddas at adot o | ||
Hofhansl, Lars | larsh at a dot o | ||
Purtell, Andrew | apurtell at a dot o | ||
Shaposhnik, Roman | rvs at a dot o | ||
Sötzutar, Enis | enis at a dot o | ||
Stack, Michael | stack at a dot o |
Contributor Workflow
Prerequisite Info
Tool set-up recommendations (git + hub): Account_Setup
Command-line instructions here assume you have "hub" installed. If you do not use "hub", you should be able to 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.
Initial Steps (need not be repeated for subsequent changes)
- Clone the trafodion repo from the GitHub mirror
- git clone git@github.com:apache/incubator-trafodion ## using ssh
or
- hub clone -p apache/incubator-trafodion ## -p option for ssh
- Fork the repo on github (https://github.com/apache/incubator-trafodion)
- hub fork
or
- (fork on web); git remote add GHuser git@github.com:GHuser/incubator-trafodion
Create a Task Branch
- Make sure you have the latest changes
- git fetch --all
- Base your branch on the latest master
- git checkout -b MyBranch origin/master
Make Changes
- Edit, Build, Test, Repeat
- You may make multiple local commits as desired. Unlike the gerrit tool, you do not need to keep your changes in a single commit.
- Depending on how long you work on the changes you may want to rebase your branch, using git rebase.
- Prior to pushing your changes to github, you may use git commands that alter your branch history:
- commit --amend, rebase, merge --squash
Push Changes to your GitHub Fork
- Push the branch to your github repo, specifying the branch (or HEAD) to push. The remote is named the same as your github user ID (created earlier by "hub fork" or "git remote add...").
- git push -n GHuser HEAD ## dry-run option to check
- git push GHuser MyBranch
- Once you publish your changes in this way, you should not subsequently use git commands that alter your branch history:
- commit --amend, rebase, merge --squash
Create a Pull Request
- Request your branch to be pulled to apache/incubator-trafodion
- hub pull-request
- Be sure to include the JIRA ID in the title of your pull request (PR). This allows all activity on the PR to be mirrored to Jira.
- [TRAFODION-12345] Cool Feature Xyz
- Automated tests are normally triggered to run on every pull request. If you are modifying something that will not affect testing, you can add a phrase to the comments of the pull request:
- jenkins, skip test
Update your Pull Request
- 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 ; .... ; git commit
- Push the branch to your github fork. These changes automatically show up in the pull-request.
- git push GHuser MyBranch
Checking Test Results
Look at the github conversation to see if automated tests have been kicked off. Normally you will see a comment from of the committers . See this link to see how tetsts get triggered:
https://wiki.trafodion.org/wiki/index.php/Committer_Workflow#Automated_Testing
When they finish there will be a comment/entry from traf-jenkins in the github page that says whether tests passed or failed. Follow the link that is right above the comment .It should look like:
"https://jenkins02.trafodion.org/job/Check-PR/<build number>"
One way to look at logs :
- The first two columns in that table are links to the specific 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 the top).(look ccarefully)
Another way to look at logs :
- The location of the logfiles is now much more predictable than it used to be.
- You can go to http://logs.trafodion.org/PullReq/
- 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.
- 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
- 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.