CI Automation: Difference between revisions

Jump to navigation Jump to search
Line 100: Line 100:


If all the builds and tests pass on the integration branch, your patch will eventually be merged into mozilla-central (these merges typically happen twice a day). At this point you're in the clear! The next time someone pulls in the latest changes from central, your changes will be included. Congratulations!
If all the builds and tests pass on the integration branch, your patch will eventually be merged into mozilla-central (these merges typically happen twice a day). At this point you're in the clear! The next time someone pulls in the latest changes from central, your changes will be included. Congratulations!
You can see all the build and test results using a service called [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central treeherder]. On the left you'll see the push information (who pushed and which commits were in the push). On the right you'll see the results. Each symbol represents a "task" which runs builds or tests. If something fails, the symbol will turn orange (or red). It's normal for every push to have a few "intermittent failures" on it. If your patch landed via phabricator, you'll be able to see it on the [https://treeherder.mozilla.org/#/jobs?repo=autoland autoland] branch of treeherder.


== [[Glossary]] ==
== [[Glossary]] ==


Mozillians use a dizzying amount of terminology that can make any new contributor's head spin. You'll often be able to find what you're looking for in the [[Glossary]]. If you come across something not mentioned there, feel free to ask us in IRC (and remind us to add it to the list).
Mozillians use a dizzying amount of terminology that can make any new contributor's head spin. You'll often be able to find what you're looking for in the [[Glossary]]. If you come across something not mentioned there, feel free to ask us in IRC (and remind us to add it to the list).
Confirmed users
656

edits

Navigation menu