Closed Bug 563828 Opened 14 years ago Closed 14 years ago

Update support-stage-new git update cron

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jsocol, Assigned: chizu)

Details

We need to add a couple steps to the cron job on mrapp-stage04 for support-stage-new that pulls Kitsune from git. Most of these are pretty trivial, but one part might need some thought: These commands need to be run from inside the virtualenv: * `./manage.py syncdb` * `schematic migrations/` These parts _don't_ need the virtualenv: * `git remote prune origin` * `git submodule update --init` * Something along the lines of: pushd locale && git pull && popd to pull updates in the locale/ submodule only. The tricky part is that we then somehow need the info from `git submodule status` to be visible to us, so we can check the revision of the submodules without needing to ping IT. I know Jeremy has the web_info_demo site on Khan, and maybe we could use that? I'm not sure what the best option is here.
(In reply to comment #0) > These commands need to be run from inside the virtualenv: > * `./manage.py syncdb` > * `schematic migrations/` Jeff suggests we shouldn't use both syncdb and schematic. Can we run `./manage.py syncdb` once and then only run schematic on cron, instead of what I said above.
chizu, would be awesome if you could lend a hand here.
Assignee: server-ops → thardcastle
At the very least, can someone run `./manage.py syncdb` by hand? The out-of-date database is blocking QA.
(In reply to comment #3) > At the very least, can someone run `./manage.py syncdb` by hand? The > out-of-date database is blocking QA. Run. (In reply to comment #0) > * Something along the lines of: > pushd locale && git pull && popd > to pull updates in the locale/ submodule only. This complains: You asked me to pull without telling me which branch you want to merge with, and 'branch..merge' in your configuration file does not tell me either. Please name which branch you want to merge on the command line and try again (e.g. 'git pull <repository> <refspec>'). See git-pull(1) for details on the refspec. > The tricky part is that we then somehow need the info from `git submodule > status` to be visible to us, so we can check the revision of the submodules > without needing to ping IT. I know Jeremy has the web_info_demo site on Khan, > and maybe we could use that? I'm not sure what the best option is here. For a quick fix, I have the cron putting the output here: http://support-stage-new.mozilla.com/env/git_submodule_status
(In reply to comment #4) > Run. Looks good, thanks! > > pushd locale && git pull && popd > This complains: Try replacing the pull with `git pull origin master`. That should fix it. > For a quick fix, I have the cron putting the output here: > http://support-stage-new.mozilla.com/env/git_submodule_status That works fine for me.
Ok, the cron changes are all working. Closing this.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to comment #6) > Ok, the cron changes are all working. Closing this. Thanks, Trevor!
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.