Closed Bug 376959 Opened 17 years ago Closed 16 years ago

Polish platform specific respin support

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Unassigned)

References

Details

Attachments

(1 file)

There are few parts to this, and I'm likely to miss something, but the rough idea is:

- be able to respin a single platform
- set up symlinks appropriately between candidate directories
- be smart about update generation and coping with symlinks
When we use symlinks, we need to use rsync -L to follow them when doing the Repack verification.
Attachment #267443 - Flags: review?(preed)
Forgot to say that it looks like the only other step using rsync is Stage, and that already got the -L treatment (where needed).
Comment on attachment 267443 [details] [diff] [review]
Follow symlinks when doing Repack verification

Do we want this to be -Lav? I believe that's what the stage step has; I can't remember if there was a reason we didn't do -a here. If there wasn't, should we standardize, so we have -a?
Attachment #267443 - Flags: review?(preed) → review+
needed for "release automation", hence marking as critical.
Severity: normal → critical
(In reply to comment #3)
> (From update of attachment 267443 [details] [diff] [review])
> Do we want this to be -Lav? I believe that's what the stage step has; I can't
> remember if there was a reason we didn't do -a here. If there wasn't, should we
> standardize, so we have -a?

I added the -a argument to standardize - it shouldn't make a difference as the metadiff is looking at the contents of the transferred archive/installer. 

Checking in Bootstrap/Step/Repack.pm;
/cvsroot/mozilla/tools/release/Bootstrap/Step/Repack.pm,v  <--  Repack.pm
new revision: 1.13; previous revision: 1.12
done

Priority: -- → P3
Assignee: build → nobody
QA Contact: mozpreed → build
Nick, what is left to do here? 
I guess we hack up the buildbot config to respin a single platform now, so point one is covered (after a fashion). TBH I don't recall all the context, so lets mark this FIXED and follow up as needed.
Status: NEW → RESOLVED
Closed: 16 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.

Attachment

General

Created:
Updated:
Size: