Closed
Bug 672818
Opened 14 years ago
Closed 14 years ago
Unhork support-release.allizom.org
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jsocol, Assigned: nmaul)
Details
With the change to our vendor library (now not a submodule, just a directory) we need to fix support-release and its update script.
3 steps:
1) Update the update script so it doesn't cd into vendor before running `git submodule sync`.
2) rm -rf vendor
3) Run update script.
Should do it.
Updated•14 years ago
|
Assignee: server-ops → jeremy.orem+bugs
Assignee | ||
Comment 1•14 years ago
|
||
I'll get this... I did support.allizom.org already, so I'm already in the loop on what's needed.
Assignee: jeremy.orem+bugs → nmaul
Assignee | ||
Comment 2•14 years ago
|
||
Completed.
This part of the update script looks like this now:
cd /data/www/support-release.allizom.org/kitsune
OLD_REV=$(git rev-parse HEAD)
git fetch -q
git checkout -q origin/next
git remote prune origin
git submodule sync
git submodule update --init --recursive
NEW_REV=$(git rev-parse HEAD)
pushd locale > /dev/null
svn revert -R .
svn up
./compile-mo.sh .
popd > /dev/null
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•