-
Notifications
You must be signed in to change notification settings - Fork 49
Some examples of IRC bot commands #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -48,8 +48,7 @@ Tags are of the format: ``YYYY.MM.DD``, | |
| .. note:: The date is the date of the push, not the date of tagging. | ||
|
|
||
| .. note:: Once addons-frontend has been tagged a new docker image will be | ||
| built on `Docker Hub | ||
| <https://hub.docker.com/r/addons/addons-frontend/builds/>`_ and is | ||
| built on `Docker Hub`_ and is | ||
| required to deploy to stage. | ||
|
|
||
| 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. | |
| Push to stage | ||
| +++++++++++++ | ||
|
|
||
| Once the tag is ready and any needed docker containers have been built, it | ||
| Once the tag is ready and any needed | ||
| `Docker Hub`_ containers have been built, it | ||
| needs to be pushed to the staging server, using the `IRC bot in #amopush | ||
| <https://mana.mozilla.org/wiki/display/SVCOPS/AMO+Dev+Resources#AMODevResources-DeployingwithJenkinsBot>`_. | ||
| Jason can help with that if needed. | ||
| Consult the IRC bot docs for more up to date information but here are examples | ||
| of commands you would run to deploy all the apps to stage: | ||
|
|
||
| * ``!build addons-stage YYYY.MM.DD`` | ||
| * ``!build admin-stage YYYY.MM.DD`` | ||
| * ``!build discopane-stage YYYY.MM.DD`` | ||
| * ``!build versioncheck-stage YYYY.MM.DD`` | ||
|
|
||
| Each of these apps live in the code respositories that are listed for tagging up | ||
| above. | ||
|
|
||
| When you run each command in ``#amopush`` you will soon see a | ||
| ``Job amo-xxxx-BUILD succeeded`` | ||
| message. Do not be fooled! This doesn't mean the change is live. You need to | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👍 |
||
| wait and watch for each ``amo-xxx-Promote succeeded`` message in ``#remora``. | ||
| The *Promote* message indicates that it's live on the server. | ||
| Here is an example of a *Promote* message to indicate the changes are live | ||
| on the server:: | ||
|
|
||
| <cloudops-hubot> amo-olympia-web-STAGE-Promote build #156 succeeded (https://deploy.mozaws.net/job/amo-olympia-web-STAGE-Promote/156/) | ||
|
|
||
| Jason can help with this if needed. | ||
|
|
||
| Before the push | ||
| +++++++++++++++ | ||
|
|
@@ -155,3 +176,5 @@ Future Goals | |
| ------------ | ||
|
|
||
| Move to continuous deployment and change the way this is done dramatically. | ||
|
|
||
| .. _`Docker Hub`: https://hub.docker.com/r/addons/addons-frontend/builds/ | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you link to those docs from here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's linked on the line above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha so it is. I'm dumb, all good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it's hard to read ReST/Sphinx diffs. I think it should be clear in the HTML.