ReleaseEngineering/SpecialRepositories: Difference between revisions

Jump to navigation Jump to search

ReleaseEngineering/SpecialRepositories (view source)

Revision as of 20:24, 10 December 2014

2,348 bytes removed ,  10 December 2014
Remove Ash and Cypress from here
(Remove Ash and Cypress from here)
Line 1: Line 1:
= Special branches =
= Special branches =
Release Engineering and the A-Team have various [[ReleaseEngineering/DisposableProjectBranches#Indefinite_booking|project branches]] booked permanently for various reasons:
Release Engineering and the A-Team have various [[ReleaseEngineering/DisposableProjectBranches#Indefinite_booking|project branches]] booked permanently for various reasons:
* Ash - where we can try mozharness patches without review
* Cypress - where we make sure that everything on the "default" branch of mozharness is running properly before merging to the "production" branch
* Cedar - where we enable test jobs that are still failing
* Cedar - where we enable test jobs that are still failing


= Cypress =
NOTE: We do not land any code on Cypress. We just sync it up with Mozilla-Central
We do not have special cases on Cypress; it has to match Mozilla-Central in every aspect except that it tests the "default" branch of mozharness.
== Re-trigger jobs ==
If you land some code on mozharness's default you should re-trigger the jobs that your changes could affect and make sure that it comes out green.
Make sure that every job that has failed on Cypress' tbpl has been re-triggered to identify intermittent oranges.
If you could star the oranges it would be super sweet.
== Sync with Mozilla-Central ==
<pre>
# Get a copy of cedar
hg clone http://hg.mozilla.org/projects/cypress
cd cypress
# Update to latest, in case someone has synced cypress since you last cloned/updated.
hg pull
# Pull latest m-c changes in
hg pull http://hg.mozilla.org/mozilla-central
# There is no need to merge
# Push to cypress
hg push ssh://hg.mozilla.org/projects/cypress
</pre>
= Ash =
You can test new Mozharness code in production by landing into [https://hg.mozilla.org/build/ash-mozharness ash-mozharness]. <br />
You can then re-trigger the jobs in [https://tbpl.mozilla.org/?tree=Ash Ash's tbpl page] by clicking on the "+" sign of a job.<br />
You should see a line on that job's summary saying which revision of ash-mozharness was used:
TinderboxPrint: ash-mozharness_revlink: https://hg.mozilla.org/build/ash-mozharness/rev/1e6478311b3f
== Checking-in and backing out ==
If you want to test something out on the gecko tree rather than the ash-mozharness tree you should back out afterward.
It makes it easier to merge m-c into Ash without conflicts.
== Merging m-c to ash ==
The same process as with Cedar:
<pre>
# Get a copy of ash
hg clone http://hg.mozilla.org/projects/ash
cd ash
# Update to latest, in case someone has updated cedar since you last cloned/updated.
# the hg up -C will blow away any local changes!
hg pull
hg up -C -r default
# Pull latest m-c changes in
hg pull http://hg.mozilla.org/mozilla-central
hg merge
hg commit -m "Merge m-c -> ash"
# Push to cedar
hg push ssh://hg.mozilla.org/projects/ash
</pre>


= Cedar =
= Cedar =
Armenzg
Confirmed users
3,990

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1039967"

Navigation menu