Update workdir for en-US checkout before updating to a given tag

RESOLVED FIXED

Status

Release Engineering
General
P2
normal
RESOLVED FIXED
8 years ago
5 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [l10n])

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

8 years ago
Created attachment 434327 [details] [diff] [review]
update workdir after pulling new changesets

When we did the clobber of the builders for 3.6.2's build3 the repackages of build2 were still going. Therefore, when the repacks for build3 happened the clobber requested had already happened.

When the repacks for build3 tried to update to FIREFOX_3_6_2_RELEASE tag the working dir (FIREFOX_BUILD2/FIREFOX_3_6_2_RELEASE) was mismatched with the local repository's (FIREFOX_BUILD3/FIREFOX_3_6_2_RELEASE).

In short, we used _BUILD2 rather than _BUILD3.

The patch attached should fix this.

The long term solution is to use Mercurial source class (bug 554438).
Attachment #434327 - Flags: review?(bhearsum)

Comment 1

8 years ago
I'd suggest to not pull -r default then.
Comment on attachment 434327 [details] [diff] [review]
update workdir after pulling new changesets

yeah, Axel is right, -r default will ruin us here, since the tag commits are on the release branch. Drop it in both the pull and update.
Attachment #434327 - Flags: review?(bhearsum) → review-
(Assignee)

Comment 3

8 years ago
Created attachment 434614 [details] [diff] [review]
update workdir after pulling new changesets
Attachment #434327 - Attachment is obsolete: true
Attachment #434614 - Flags: review?(bhearsum)
Attachment #434614 - Flags: review?(bhearsum) → review+
(Assignee)

Updated

8 years ago
Priority: -- → P2
(Assignee)

Comment 4

8 years ago
Comment on attachment 434614 [details] [diff] [review]
update workdir after pulling new changesets

http://hg.mozilla.org/build/buildbotcustom/rev/5b165130854b
Attachment #434614 - Flags: checked-in+
(Assignee)

Updated

8 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.