Closed Bug 725889 Opened 13 years ago Closed 13 years ago

start_uptake_monitoring builder triggers both ready-for-release and ready-for-releasetest

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 729918

People

(Reporter: lsblakk, Assigned: rail)

Details

(Whiteboard: [automation][releases])

I think this should only trigger one or the other? Perhaps we should pass in a param for which uptake to monitor for? In any case, I just forced it to trigger ready-for-releasetest (we have pushed to internal mirrors only) and it kicked off both and sent email to r-d saying we were ready for release. http://buildbot-master07.build.sjc1.mozilla.com:8001/builders/release-mozilla-release-start_uptake_monitoring/builds/0
2012-02-09 16:50:30-0800 [HTTPPageGetter,client] TriggerBouncerCheck: uptake is 123546 2012-02-09 16:50:30-0800 [HTTPPageGetter,client] TriggerBouncerCheck: Stopping uptake monitoring: Reached required uptake: 123546 2012-02-09 16:50:30-0800 [HTTPPageGetter,client] TriggerBouncerCheck: polling finished 2012-02-09 16:50:30-0800 [HTTPPageGetter,client] Stopping factory <HTTPClientFactory: https://bounceradmin.mozilla.com/api//uptake/?product=Firefox-10.0&os=w in> 2012-02-09 16:50:30-0800 [HTTPPageGetter,client] Stopping factory <HTTPClientFactory: https://bounceradmin.mozilla.com/api//uptake/?product=Firefox-10.0-Comp lete&os=win>
hmm, script_repo_revision FIREFOX_10_0_RELEASE Builder
Component: Release Engineering → Release Engineering: Automation
OS: Mac OS X → All
QA Contact: release → catlee
Hardware: x86 → All
I think you're fixing this elsewhere?
Assignee: nobody → rail
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.