Skip to content

Commit 895890b

Browse files
committed
Some examples of IRC bot commands
1 parent 4d04c01 commit 895890b

File tree

1 file changed

+27
-4
lines changed

1 file changed

+27
-4
lines changed

docs/server/push-duty.rst

Lines changed: 27 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,7 @@ Tags are of the format: ``YYYY.MM.DD``,
4848
.. note:: The date is the date of the push, not the date of tagging.
4949

5050
.. note:: Once addons-frontend has been tagged a new docker image will be
51-
built on `Docker Hub
52-
<https://hub.docker.com/r/addons/addons-frontend/builds/>`_ and is
51+
built on `Docker Hub`_ and is
5352
required to deploy to stage.
5453

5554
It's usually the master branch that is tagged::
@@ -99,10 +98,32 @@ Then update the etherpad with the new comparison link for the updated tag.
9998
Push to stage
10099
+++++++++++++
101100

102-
Once the tag is ready and any needed docker containers have been built, it
101+
Once the tag is ready and any needed
102+
`Docker Hub`_ containers have been built, it
103103
needs to be pushed to the staging server, using the `IRC bot in #amopush
104104
<https://mana.mozilla.org/wiki/display/SVCOPS/AMO+Dev+Resources#AMODevResources-DeployingwithJenkinsBot>`_.
105-
Jason can help with that if needed.
105+
Consult the IRC bot docs for more up to date information but here are examples
106+
of commands you would run to deploy all the apps to stage:
107+
108+
* ``!build addons-stage YYYY.MM.DD``
109+
* ``!build admin-stage YYYY.MM.DD``
110+
* ``!build discopane-stage YYYY.MM.DD``
111+
* ``!build versioncheck-stage YYYY.MM.DD``
112+
113+
Each of these apps live in the code respositories that are listed for tagging up
114+
above.
115+
116+
When you run each command in ``#amopush`` you will soon see a
117+
``Job amo-xxxx-BUILD succeeded``
118+
message. Do not be fooled! This doesn't mean the change is live. You need to
119+
wait and watch for each ``amo-xxx-Promote succeeded`` message in ``#remora``.
120+
The *Promote* message indicates that it's live on the server.
121+
Here is an example of a *Promote* message to indicate the changes are live
122+
on the server:
123+
124+
<cloudops-hubot> amo-olympia-web-STAGE-Promote build #156 succeeded (https://deploy.mozaws.net/job/amo-olympia-web-STAGE-Promote/156/)
125+
126+
Jason can help with this if needed.
106127

107128
Before the push
108129
+++++++++++++++
@@ -155,3 +176,5 @@ Future Goals
155176
------------
156177

157178
Move to continuous deployment and change the way this is done dramatically.
179+
180+
.. _`Docker Hub`: https://hub.docker.com/r/addons/addons-frontend/builds/

0 commit comments

Comments
 (0)