Closed
Bug 1060442
Opened 10 years ago
Closed 10 years ago
Datazilla Repository Update
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jeads, Assigned: cliang)
References
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1154] )
A new datazilla repository is ready to push to stage. This release includes the following changes: 1.) Broadened the regex matching revisions to include the following characters in addition to alphanumerics: "." and "-". "^raw/(?P<branch>.+)/(?P<revision>[a-zA-Z0-9_.-]+)/?$" https://github.com/mozilla/datazilla/blob/master/datazilla/webapp/apps/datazilla/testdata/urls.py#L6 This is in support of the datazilla mozbench project.
Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-webops → cliang
Assignee | ||
Comment 1•10 years ago
|
||
In staging, I pushed out commit 11fe1ceb29a2de042186a6c4b21437ad4c8809b8. Please let me know when you've completed your testing and are happy with this change going into production. $ sudo ./update Updating code... Cleaning gitignore and pyc files... Storing revision information... ./update: line 40: /data/datazilla-stage/src/datazilla.allizom.org/datazilla/media/revision: No such file or directory ./update: line 43: /data/datazilla-stage/src/datazilla.allizom.org/datazilla/media/revision_info.txt: No such file or directory Deploying code... [2014-08-29 10:15:20] Running rsync_project [2014-08-29 10:15:20] [localhost] running: /usr/bin/rsync -aq --include '.gitkeep' --exclude '.git*' --exclude '.hg*' --exclude '.svn*' --exclude 'CVS' --exclude '.bzr*' --delete /data/datazilla-stage/src/datazilla.allizom.org/ /data/datazilla-stage/www/datazilla.allizom.org/ [2014-08-29 10:15:21] [localhost] finished: /usr/bin/rsync -aq --include '.gitkeep' --exclude '.git*' --exclude '.hg*' --exclude '.svn*' --exclude 'CVS' --exclude '.bzr*' --delete /data/datazilla-stage/src/datazilla.allizom.org/ /data/datazilla-stage/www/datazilla.allizom.org/ (1.140s) [2014-08-29 10:15:21] Finished rsync_project (1.140s) [2014-08-29 10:15:21] Running commit_www [2014-08-29 10:15:21] [localhost] running: cd /data/datazilla-stage/www && /usr/bin/git add .; /usr/bin/git commit -a -m 'deploy ['datazilla.allizom.org']' [2014-08-29 10:15:21] [localhost] finished: cd /data/datazilla-stage/www && /usr/bin/git add .; /usr/bin/git commit -a -m 'deploy ['datazilla.allizom.org']' (0.202s) [localhost] out: [master 8b8de6b] deploy [datazilla.allizom.org] [localhost] out: 1 file changed, 1 insertion(+), 1 deletion(-) [2014-08-29 10:15:21] Finished commit_www (0.202s) [2014-08-29 10:15:21] Running push_www [2014-08-29 10:15:21] [datazilla1.stage.webapp.scl3.mozilla.com] running: /data/bin/update-www.sh datazilla.allizom.org [2014-08-29 10:15:23] [datazilla1.stage.webapp.scl3.mozilla.com] finished: /data/bin/update-www.sh datazilla.allizom.org (1.777s) [2014-08-29 10:15:23] Finished push_www (1.779s) [2014-08-29 10:15:23] Starting new HTTPS connection (1): changelog.paas.allizom.org Touching the wsgi file locally... [2014-08-29 10:15:23] [datazilla1.stage.webapp.scl3.mozilla.com] running: touch /data/www/datazilla.allizom.org/datazilla/datazilla/wsgi.py [2014-08-29 10:15:24] [datazilla1.stage.webapp.scl3.mozilla.com] finished: touch /data/www/datazilla.allizom.org/datazilla/datazilla/wsgi.py (0.335s)
Reporter | ||
Comment 2•10 years ago
|
||
Stage looks good. Please go ahead and push the updated repository to production.
Assignee | ||
Comment 3•10 years ago
|
||
Pushed commit 11fe1ceb29a2de042186a6c4b21437ad4c8809b8 out to production. $ sudo ./update Updating code... Cleaning gitignore and pyc files... Storing revision information... ./update: line 40: /data/datazilla/src/datazilla.mozilla.org/datazilla/media/revision: No such file or directory ./update: line 43: /data/datazilla/src/datazilla.mozilla.org/datazilla/media/revision_info.txt: No such file or directory Deploying code... [2014-08-29 13:42:14] Running rsync_project [2014-08-29 13:42:14] [localhost] running: /usr/bin/rsync -aq --include '.gitkeep' --exclude '.git*' --exclude '.hg*' --exclude '.svn*' --exclude 'CVS' --exclude '.bzr*' --delete /data/datazilla/src/datazilla.mozilla.org/ /data/datazilla/www/datazilla.mozilla.org/ [2014-08-29 13:42:16] [localhost] finished: /usr/bin/rsync -aq --include '.gitkeep' --exclude '.git*' --exclude '.hg*' --exclude '.svn*' --exclude 'CVS' --exclude '.bzr*' --delete /data/datazilla/src/datazilla.mozilla.org/ /data/datazilla/www/datazilla.mozilla.org/ (1.681s) [2014-08-29 13:42:16] Finished rsync_project (1.682s) [2014-08-29 13:42:16] Running commit_www [2014-08-29 13:42:16] [localhost] running: cd /data/datazilla/www && /usr/bin/git add .; /usr/bin/git commit -a -m 'deploy ['datazilla.mozilla.org']' [2014-08-29 13:42:16] [localhost] finished: cd /data/datazilla/www && /usr/bin/git add .; /usr/bin/git commit -a -m 'deploy ['datazilla.mozilla.org']' (0.293s) [localhost] out: [master f2e39fb] deploy [datazilla.mozilla.org] [localhost] out: 1 file changed, 1 insertion(+), 1 deletion(-) [2014-08-29 13:42:16] Finished commit_www (0.293s) [2014-08-29 13:42:16] Running push_www [2014-08-29 13:42:16] [datazilla1.webapp.scl3.mozilla.com] running: /data/bin/update-www.sh datazilla.mozilla.org [2014-08-29 13:42:17] [datazilla1.webapp.scl3.mozilla.com] finished: /data/bin/update-www.sh datazilla.mozilla.org (0.917s) [2014-08-29 13:42:17] Finished push_www (0.918s) [2014-08-29 13:42:17] Starting new HTTPS connection (1): changelog.paas.allizom.org [2014-08-29 13:42:17] [datazilla1.webapp.scl3.mozilla.com] running: touch /data/www/datazilla.mozilla.org/datazilla/datazilla/wsgi.py [2014-08-29 13:42:18] [datazilla1.webapp.scl3.mozilla.com] finished: touch /data/www/datazilla.mozilla.org/datazilla/datazilla/wsgi.py (0.337s)
Assignee | ||
Comment 4•10 years ago
|
||
Closing this bug for now. Please reopen if it turns out that something went awry with the push.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•