Closed Bug 1285319 Opened 9 years ago Closed 9 years ago

[ship-it] Change ship-it repo URL in chef

Categories

(Infrastructure & Operations :: IT-Managed Tools, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: ericz)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3181])

From bug 1283640 comment #7: > we want to use github.com instead of git.m.o in chief for ship-it > (http://genericadm.private.phx1.mozilla.com/chief/shipit.prod and > http://genericadm.private.phx1.mozilla.com/chief/shipit.stage). Please switch upstream to: https://github.com/mozilla-releng/ship-it.git This blocks the decom of git.mozilla.org (bug 1277297) which was originally announced[1] for June 27 (on June 1) [1] https://groups.google.com/d/msg/mozilla.dev.version-control/H6_TWlWPQGk/abchYZWgNQAJ
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3181]
Assignee: server-ops-webops → eziegenhorn
I noticed the update script for this site isn't working because git head is currently * (no branch) bc2c01d Bug 1178331 - kill ship it notifier (#76) which when the script does a git pull fails because it isn't on a branch. Should we checkout the master branch perhaps?
I think this is how chief checks out the code. bc2c01d was the last commit I deployed (yesterday).
I'll keep looking at that. I see the dev site hard codes the repo in the update scripts, we want to switch that to github too I take it?
yes, all of them should switch to github, so we can kill git.m.o :)
Dev, stage and prod are all switched to github. Let me know if there are any issues.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.