1346237 - Deploy orangefactor 5c74a2f26b23 to pick up bug 1344387

Status: RESOLVED FIXED

(Tree Management Graveyard :: OrangeFactor, enhancement, P1)

Description

[Ed Morley [:emorley]]

https://hg.mozilla.org/automation/orangefactor/rev/5c74a2f26b23

Comment 1

[Ed Morley [:emorley]]

[[e-mail]3 ~]$ sudo su webtools -
[[e-mail]3 emorley]$ cd ~/apps/orangefactor/src/orangefactor/ && hg pull -uv
pulling from https://hg.mozilla.org/automation/orangefactor/
warning: hg.mozilla.org certificate with fingerprint 73:7f:ef:ab:68:0f:49:3f:88:91:f0:b7:06:69:fd:8f:f2:55:c9:56 not verified (check hostfingerprints or web.cacerts config setting)
searching for changes
all local heads known remotely
adding changesets
adding manifests
adding file changes
added 1 changesets with 2 changes to 2 files
resolving manifests
getting templates/bug_comment.template
getting woo_commenter.py
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
[[e-mail]3 orangefactor]$ exit
[[e-mail]3 ~]$ sudo service orangefactor restart
usage: /etc/init.d/orangefactor {start|stop}
[[e-mail]3 ~]$ sudo service orangefactor stop; sudo service orangefactor start
stopping orangefactor                                      [  OK  ]
starting orangefactor                                      [  OK  ]

(gbrown: Note for future deploys, if there were web assets modified, in addition the deploy.sh script would need running to copy the files to the /usr/share/nginx/html/ directory. See root's bash history for examples of how to do that)

Comment 2

[Ed Morley [:emorley]]

In fact in this case, I didn't need to restart the orangefactor service either, since this wasn't an API change, but a change to a file only run via cron.