info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Workflow for pinning mozharness from the tree
0 views
Skip to first unread message
Armen Zambrano G.
Mar 25, 2015, 9:44:51 AM3/25/15
to Sheriffs, Dave Hunt
I'm asking dhunt to create a head in mozharness for the change he needs
on b2g37_v2_2. I told him to wait one last second to make sure that we
are in agreement.
https://bugzilla.mozilla.org/show_bug.cgi?id=1143634#c10
b2g37_v2_2 will be pointing to such head.
On 15-02-02 05:18 PM, Armen Zambrano G. wrote:
> (Follow ups to mozilla.release.engineering)
>
> Hello all,
> As you probably know, I have been rolling out with rail the pinning of
> mozharness to various trees. Soon we will have all trunk trees and then
> the remaining trees.
>
> I want to discuss and agree on how we will roll changes into mozharness
> and pin them from the tree (rather than all jobs running from the
> "production" branch).
>
> If it helps to the discussion, talos has followed this approach for over
> 3 years. The amount of times that specific changes were needed on
> release trees were minimal. Branching was not needed.
>
> Proposal: I believe we can simply let mozharness.json changes go through
> the uplift process and create new heads or tag heads if need be.
> I believe that we won't need to do have branches in mozharness for older
> release branches.
>
> I am not familiar anymore on how release jobs use mozharness.
> If I understand correctly, we tag mozharness in the production branch
> and use that. I don't know what changes (if any) would be needed to
> support pinning instead of tags (if we would want that).
>
> For what reasons would we still need to merge to the "production" branch?
>
> regards,
> Armen
>
--
Zambrano Gasparnian, Armen
Automation & Tools Engineer
http://armenzg.blogspot.ca
on b2g37_v2_2. I told him to wait one last second to make sure that we
are in agreement.
https://bugzilla.mozilla.org/show_bug.cgi?id=1143634#c10
b2g37_v2_2 will be pointing to such head.
On 15-02-02 05:18 PM, Armen Zambrano G. wrote:
> (Follow ups to mozilla.release.engineering)
>
> Hello all,
> As you probably know, I have been rolling out with rail the pinning of
> mozharness to various trees. Soon we will have all trunk trees and then
> the remaining trees.
>
> I want to discuss and agree on how we will roll changes into mozharness
> and pin them from the tree (rather than all jobs running from the
> "production" branch).
>
> If it helps to the discussion, talos has followed this approach for over
> 3 years. The amount of times that specific changes were needed on
> release trees were minimal. Branching was not needed.
>
> Proposal: I believe we can simply let mozharness.json changes go through
> the uplift process and create new heads or tag heads if need be.
> I believe that we won't need to do have branches in mozharness for older
> release branches.
>
> I am not familiar anymore on how release jobs use mozharness.
> If I understand correctly, we tag mozharness in the production branch
> and use that. I don't know what changes (if any) would be needed to
> support pinning instead of tags (if we would want that).
>
> For what reasons would we still need to merge to the "production" branch?
>
> regards,
> Armen
>
--
Zambrano Gasparnian, Armen
Automation & Tools Engineer
http://armenzg.blogspot.ca
Armen Zambrano G.
Mar 25, 2015, 9:57:26 AM3/25/15
to mozilla-relea...@lists.mozilla.org
bhearsum rightly so recommends that we branch in these cases.
Otherwise, we would have 2 heads for one branch and could be confusing
when buildduty wants to merge default to production.
Anyone has any objections to create a b2g37_v2_2 branch?
Otherwise, we would have 2 heads for one branch and could be confusing
when buildduty wants to merge default to production.
Anyone has any objections to create a b2g37_v2_2 branch?
Armen Zambrano G.
Mar 26, 2015, 1:18:14 PM3/26/15
to mozilla-relea...@lists.mozilla.org, Dave Hunt
Since I have not heard any objections I will go ahead and create the
mozilla-b2g37_v2_2 branch.
mozilla-b2g37_v2_2 branch.
0 new messages