Closed Bug 672192 Opened 14 years ago Closed 14 years ago

deploy new talos.zip bundle

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: anodelman, Assigned: armenzg)

References

Details

No description provided.
Blocks: 609111, 488298
Staged green over the weekend. This is ready for deployment.
The changes included in the zip will not affect current talos numbers - they either are inactive or only handle browser management and do not touch the running test.
(In reply to comment #3) > The changes included in the zip will not affect current talos numbers - they > either are inactive or only handle browser management and do not touch the > running test. In other words, no downtime involved and it can be deployed at any given time, right? Does it have to wait for xperf to actually be deployed on the machines? Would Wednesday or Thursday morning work for you?
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Priority: -- → P2
It can be rolled out without downtime. It does not need to block on xperf rollout, the xperf code is inactive for now.
Priority: P2 → --
Priority: -- → P2
In build.m.o:/var/www/html/build/talos/zips wget -Otalos.bug672192.zip http://people.mozilla.org/~anodelman/taloszips/c5e493459dd0/talos.zip rm talos.zip && ln -s talos.bug672192.zip talos.zip mv talos.bug658392.zip old/ Notified developers in mailing list just in case: http://groups.google.com/group/mozilla.dev.tree-management/browse_thread/thread/a966e2f03c67b28f# Updated maintenance page: https://wiki.mozilla.org/index.php?title=ReleaseEngineering:Maintenance&action=history
Status: ASSIGNED → RESOLVED
Closed: 14 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.