Closed Bug 554737 Opened 15 years ago Closed 15 years ago

oldRepoPath in ReleaseUpdatesFactory should fall back to repoPath, not mozRepoPath

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kairo, Assigned: kairo)

References

Details

Attachments

(1 file)

As mentioned in bug 492913 comment #53, the SeaMonkey and Thunderbird buildbots don't work with the current ReleaseUpdatesFactory implementation unless oldRepoPath is explicitely specified. The fallback should not be the mozRepoPath that points to the Mozilla platform repo in our builds, but the repoPath that points to the main/application repo.
This should do it. I haven't actively tested it, as I have no release to run and no staging environment, could you guys run it through staging as well?
Attachment #434650 - Flags: review?(bhearsum)
Someone will be doing a staging release run in bug 557819. We should be able to test this patch at that time.
Blocks: 557819
Comment on attachment 434650 [details] [diff] [review] fall back to repoPath instead Seems to work fine.
Attachment #434650 - Flags: review?(bhearsum) → review+
Comment on attachment 434650 [details] [diff] [review] fall back to repoPath instead changeset: 700:9cb48082972a
Attachment #434650 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 15 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

Creator:
Created:
Updated:
Size: