Closed Bug 743274 Opened 14 years ago Closed 14 years ago

Off schedule push of updated code to bugzilla.mozilla.org

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dkl, Assigned: jd)

References

Details

Can we please get a bmo production push? This is for a critical task that needs to happen before the normal update window next week. checksetup.pl : no schema changes: none revisions : 8120 8121 8122 8123 thanks dkl
please hold off on this for a short bit. I need to make some additional changes. Will let you know to start this later today. dkl
David, I can do this whenever you need, just update this bug. Regards
Assignee: server-ops-devservices → jcrowe
Status: NEW → ASSIGNED
QA Contact: shyam → cshields
(In reply to Jason Crowe [:jd] from comment #2) > David, > > I can do this whenever you need, just update this bug. > > Regards Okay. I am ready now. Please push this live as soon as possible. checksetup.pl : no schema changes: none revisions : 8120 8121 8122 8123 8124 dkl
David, I cannot seem to get correct access to bzr. Can you run the following command and let me know when it is done? I can update from there. (Replace your email of course). bzr tag -d bzr+ssh://EMAIL@mozilla.com@bzr.mozilla.org/bmo/4.0/ -rtag:current-staging --force current-production I already ran the tests and things are looking good except every time I run this command I get a 'Permission denied ERROR: Cannot lock LockDir'. I just need the tag updated so I can run the update scripts. Please let me know if there are any issues.
(In reply to Jason Crowe [:jd] from comment #4) > bzr tag -d bzr+ssh://EMAIL@mozilla.com@bzr.mozilla.org/bmo/4.0/ > -rtag:current-staging --force current-production done
David, The push is now complete, please let us know if you run into trouble. Regards Jason
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.