tl;dr; Next week, I would like to make all jobs on all trees stop using
the "production" branch of mozharness. Instead I want them to be pinned
to a specific version of mozharness.
Hello all,
Some of you may be aware that Mozharness runs a lot of jobs on
treeherder. You might also know that a change on the mozharness
repository would affect all jobs in every tree. This means that release
branches could start failing since trunk code is different.
In order to eliminate these issues, we have been rolling out to all
trees something that we call "pinning mozharness".
This allows us to check out a specific revision of mozharness based on
information from the tree.
We now will be able to stop using the "production" branch and instead
bump the revision when we need new code deployed.
This also means that you will be able to see on the tree when new
mozharness code is deployed. This means that we can also back it out
like any other change.
For developer's workflow this might simply mean the trees will be open
for longer windows. For sheriffs it will be very sweet (I hope!). For
people hacking mozharness it will also have the benefit of not having to
worry about supporting older code.
I would like to stop using the "production" branch of mozharness on all
trees next week (aka pin mozharness to a specific revision).
If you want to understand this change more you can read about it in here:
http://armenzg.blogspot.ca/2014/11/pinning-mozharness-from-in-tree-aka.html
regards,
Armen
--
Zambrano Gasparnian, Armen
Automation & Tools Engineer
http://armenzg.blogspot.ca
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
