Closed Bug 670660 Opened 9 years ago Closed 9 years ago

major update verify builders are broken

Categories

(Release Engineering :: General, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: rail)

References

Details

(Whiteboard: [automation][releases])

Attachments

(2 files, 1 obsolete file)

The major update builder bumps the verify configs, and then tags them based on the majorUpdateBaseTag variable. However, the major update verify builders update the configs based on the plain "baseTag" variable. So, they end up getting the wrong configs.
Priority: -- → P2
Whiteboard: [automation][releases]
Assignee: nobody → rail
Attached patch use majorUpdateBaseTag (obsolete) — Splinter Review
To be tested.
Attachment #546727 - Attachment is obsolete: true
Attachment #546729 - Flags: review?(bhearsum)
Attachment #546730 - Flags: review?(bhearsum)
3.6.10 -> 5.0 MU verify factory set script_repo_revision to FIREFOX_5_0_RELEASE_RUNTIME in staging.
Attachment #546730 - Flags: review?(bhearsum) → review+
Attachment #546729 - Flags: review?(bhearsum) → review+
Status: NEW → RESOLVED
Closed: 9 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.