Closed Bug 554439 Opened 11 years ago Closed 11 years ago

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

Categories

(Release Engineering :: General, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: armenzg)

Details

(Whiteboard: [l10n])

Attachments

(1 file, 1 obsolete file)

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)
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-
Attachment #434327 - Attachment is obsolete: true
Attachment #434614 - Flags: review?(bhearsum)
Attachment #434614 - Flags: review?(bhearsum) → review+
Priority: -- → P2
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+
Status: ASSIGNED → RESOLVED
Closed: 11 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.