Skip to content
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.

Sign up for GitHub

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

#319 - Cleaning up ci.md #320

Merged
merged 2 commits into from
Aug 18, 2016
Merged

#319 - Cleaning up ci.md #320

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8b2c15
#319 Fix some grammar and spelling mistakes in the CI file
webkenny Aug 18, 2016
91715e3
#319 Be sure it is clear to the reader than they need to be a reposit…
webkenny Aug 18, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions readme/ci.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Travis CI can be used to deploy a fully built site artifact (with the docroot) i
2. Travis builds the docroot
3. Travis commits the docroot to a specific "build" branch and pushes to Acquia Cloud

To set up this workflow, you must configure Acquia Cloud, GitHub, and Travis CI to work together. Step-by-step instructions are provided below. _The following instructins apply only to private GitHub repositories._
To set up this workflow, you must configure Acquia Cloud, GitHub, and Travis CI to work together. Step-by-step instructions are provided below. _The following instructions apply only to private GitHub repositories._


1. Generate an SSH key locally. E.g.,
Expand All @@ -41,14 +41,14 @@ To set up this workflow, you must configure Acquia Cloud, GitHub, and Travis CI
ssh-keygen -t rsa -b 4096

Do not use a passphrase!

1. Create a new Acquia Cloud account to be used exclusively as a container for the SSH keys that will grant Travis push access to Acquia Cloud. This can be done by inviting a new team member on the "Teams" tab in Acquia Cloud. You can use an email address like `<email>[email protected]`. The team member must have SSH push access.
1. Login the your new Acquia Cloud account and add the public SSH key from the key pair that was generated in step 1 by visiting `https://accounts.acquia.com/account/[uid]/security`.
1. Add the same public SSH key to the "Deployment Keys" section on your project's GitHub settings page, located at `https://github.com/acquia-pso/[project-name]/settings/keys`.
1. Login to the new Acquia Cloud account and add the public SSH key from the key pair that was generated in step 1 by visiting `https://accounts.acquia.com/account/[uid]/security`.
1. Add the same public SSH key to the "Deployment Keys" section on your project's GitHub settings page, located at `https://github.com/acquia-pso/[project-name]/settings/keys`. **Note: You may not have direct access to these settings if you do not have administrative control over your repository.**
1. Add the _private SSH key_ to your project's Travis CI settings located at `https://magnum.travis-ci.com/acquia-pso/[project-name]/settings`.
1. Uncomment the example deployment steps in your .travis.yml file and customize them to deploy your desired branch.
1. Add your cloud git repository to the remotes section of your project.yml file:

remotes:
- [email protected]:example.git`

Expand Down