-
Notifications
You must be signed in to change notification settings - Fork 214
ACME workflow
James Foucar edited this page Aug 24, 2016
·
8 revisions
Steps:
- If you're on a machine for which baselines are maintained go to step 4
- Clone ACME / Checkout master and pull
- Update baselines for acme_developer: create_test -g acme_developer
- Create your feature branch, make commits
- Test your feature branch against master baselines: create_test -c -b master acme_developer
- If all PASS, submit pull request
Integration:
- The integrator reviews the code and merges the feature branch to our "next" branch
- Nightly Jenkins processes run the next branch on a number of systems
- If the tests above had no new fails or unexpected diffs, go to step 6
- Testing czar bisects next branch on machine with new fails/diffs, notify the developer of the branch flagged by bisect that their branch caused problems
- Developer makes fixes to their branch, go back to integration step 1
- Expected diffs are blessed
- Merge feature branch to master
- Expected diffs are blessed to master baselines next day