Skip to content

ACME workflow

James Foucar edited this page Aug 24, 2016 · 8 revisions

Steps:

  1. If you're on a machine for which baselines are maintained go to step 4
  2. Clone ACME / Checkout master and pull
  3. Update baselines for acme_developer: create_test -g acme_developer
  4. Create your feature branch, make commits
  5. Test your feature branch against master baselines: create_test -c -b master acme_developer
  6. If all PASS, submit pull request

Integration:

  1. The integrator reviews the code and merges the feature branch to our "next" branch
  2. Nightly Jenkins processes run the next branch on a number of systems
  3. If the tests above had no new fails or unexpected diffs, go to step 6
  4. 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
  5. Developer makes fixes to their branch, go back to integration step 1
  6. Expected diffs are blessed
  7. Merge feature branch to master
  8. Expected diffs are blessed to master baselines next day
Clone this wiki locally