Mozillians/Releases/Process: Difference between revisions

Mozillians/Releases/Process (view source)

34 bytes added , 5 February 2013

no edit summary

Confirmed users

583

edits

@@ Line 16: / Line 16: @@
 * A second developer with repository administration privileges reviews the new code and, if it is satisfactory, [[/Web_Testing/Automation/CodeReviewProcess#How_to_do_a_merge.3F | merges]] it into the /mozilla/mozillians repository on GitHub.
 ** QA engineers may [[/Web_Testing/Automation/CodeReviewProcess | monitor code]] merged to the /mozilla/mozillians repository on GitHub.
-* Within 15 minutes, the continuous integration service (Jenkins) checks out the merged code, builds it, and [https://ci.mozilla.org/job/mozillians/ publishes the status].
+* Within 15 minutes, the continuous integration service (Jenkins) checks out the merged code, builds it, runs any unit tests, and [https://ci.mozilla.org/job/mozillians/ publishes the status of the build].
 * Only if Jenkins tests pass, the code is deployed on the [https://mozillians-dev.allizom.org/en-US/ development server] and any commits with the appropriate commit message are changed in bugzilla to "RESOLVED/FIXED".
 * Prior to the release date, and in coordination with a QA engineer, a developer with the appropriate permissions pushes the release to staging.