Closed
Bug 412006
Opened 17 years ago
Closed 14 years ago
should use tagged version of signing tools, not HEAD
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Unassigned)
References
Details
This really caused us headaches during the FF3.0beta2 release.
Comment 1•17 years ago
|
||
According to the doc and the code, tag support is already there for the thing that bit us (bug 407962), "--release FIREFOX_3_0b2_RELEASE" (this is in the signing doc s well). However, signing tools were broken in this tag (fixed in bug 375415). There are several problems here: * we don't use the latest update-packaging tools anywhere else, we use a static tag (formerly MOZILLA_1_9a2_RELEASE, now UPDATE_PACKAGING_R1). * the signing doc checks out a lot of tools, mostly from HEAD We can just update the doc to pull the right mish-mash of versions, but there are a lot of manual steps in there that just don't need to be; we should automate this (bug 409479), as it's going to be hard to keep the doc up to date and working on different products and branches.
Depends on: 409479
Reporter | ||
Comment 2•17 years ago
|
||
Manually pulling mish-mash versions was ugly for beta2, so I'd rather not relive that if possible. Until we sort this out, could we manually apply a static tag on the right mish-mash of versions? That way, when we are in the midst of beta3, we can easily see what to pull, and know thats exactly what we already pre-tested? (Its also easier to doc!)
Comment 3•17 years ago
|
||
(In reply to comment #2) > Manually pulling mish-mash versions was ugly for beta2, so I'd rather not > relive that if possible. > > Until we sort this out, could we manually apply a static tag on the right > mish-mash of versions? That way, when we are in the midst of beta3, we can > easily see what to pull, and know thats exactly what we already pre-tested? > > (Its also easier to doc!) Hm, let me investigate a bit more. I think we probably cannot, because we need the current tagged release for the upx installer stuff. We could use e.g. UPDATE_PACKAGING_R1 for everything else, but the signing script doesn't know how to do that (just uses the same tag for all checkouts, afaict).
Updated•17 years ago
|
Priority: -- → P3
Reporter | ||
Comment 4•16 years ago
|
||
Triaged to Future.
Component: Release Engineering → Release Engineering: Future
QA Contact: build → release
Summary: automation should use tagged version of signing tools, not HEAD → should use tagged version of signing tools, not HEAD
Comment 5•14 years ago
|
||
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Comment 6•14 years ago
|
||
We've been doing this for awhile!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•