If you use Git, you may want to host your Git repository at GitHub or on Bitbucket to take advantage of their excellent Git support, pull requests with integrated code review, and use other features. The following methods are available to keep your application’s code in GitHub or Bitbucket while still hosting it on Cloud Platform:
Pipelines provides integration with GitHub, Bitbucket, and the Cloud Platform interface.
Manually creating two remotes for your local repository clone: one at GitHub or Bitbucket, and one at Cloud Platform.
Using GitHub with Cloud Platform
The first step is to create two remote repositories. Suppose you have an existing repository at GitHub containing your application’s code. Use the following commands to make a local clone:
GitHub is the origin remote, the default location for gitpush and gitpull.
To deploy this code to Cloud Platform, add your Cloud Platform repository as an additional remote, named something short, like ac, and then do an initial gitpush--forceac to reinitialize the Cloud Platform repository. You can find the URL of your Cloud Platform repository in the Cloud Platform interface, using Application info panel.
Now you have two remotes, origin (GitHub) and ac (Cloud Platform).
Pushing changes
After you have set up your two remote repositories, keep them in sync by pushing local changes to both GitHub and Cloud Platform. You can edit some files and push them to GitHub:
You can also push the same changes to Cloud Platform:
git push ac master
Your new code is now in both your GitHub and Cloud Platform repositories and is running on your Cloud Platform application.
Synchronizing release tags
Suppose that now you deploy your code on Cloud Platform from the Development environment (running the master branch) to Production. This creates a new release tag in your Cloud Platform repository that shows you exactly what code you deployed that day. You do not have to synchronize that release tag to GitHub, but you can:
git pull ac
From svn-18.devcloud.hosting.acquia.com:mysite
* [new tag] 2012-03-12 -> 2012-03-12
git push --tags
Now your GitHub repository contains the same release tag as your Cloud Platform repository.
Translating your root directory with git subtree
Cloud Platform requires that you keep all of your Drupal application code in the directory docroot in your repository. Your existing GitHub repository may not be set up that way, and you may have a lot of commit history in that repository that you want to preserve. To preserve your GitHub repository’s directory structure and commit history, you can use gitsubtree to translate your GitHub repository’s root directory into a Cloud Platform docroot directory.
Using BitBucket with Cloud Platform
Here is how to make your Cloud Platform code repository available on Bitbucket as well:
Create an account on bitbucket.org. Bitbucket offers unlimited private repositories for free for up to five users. During the account creation process, select the empty repository option and provide it with a name.
Once your account has been created and your empty repository is provisioned, add your SSH public key to Bitbucket under your account settings. You can either use an existing key or generate a new key pair for Bitbucket use only.
On your Bitbucket repository overview page, under Command line, click I have an existing project and copy the remote URL, which should appear similar to the following:
On your local command line, navigate to your Cloud Platform repository directory and run the following to add a new remote named bitbucket. Of course, you’ll need to replace the git@bitbucket location with the actual one you copied from your repository overview page; you can also name the new remote whatever you’d like:
Push all of your code, including branches and tags, to your new Bitbucket remote repository:
git push -u bitbucket --all
When prompted for a password, which is only necessary the first time you connect, enter your actual Bitbucket account password before you proceed with the push.
When you refresh your repository overview on Bitbucket, you should now see all of your code and commits.
If you want to keep your Cloud Platform and Bitbucket repositories in sync, create a new alias named all in the .git/config file in your repository:
You can find the URL of your Cloud Platform repository in the Cloud Platform interface’, using the Application info panel.
When you push new commits, use the all alias to push simultaneously code to both Cloud Platform and Bitbucket:
git push all
Connecting to JIRA
JIRA is Atlassian’s issue tracking and project management software. For information about how to connect your remote Bitbucket or GitHub repository to JIRA, see Atlassian’s documentation.
If you use Git, you may want to host your Git repository at GitHub or on Bitbucket to take advantage of their excellent Git support, pull requests with integrated code review, and use other features. The following methods are available to keep your application’s code in GitHub or Bitbucket while still hosting it on Cloud Platform:
Pipelines provides integration with GitHub, Bitbucket, and the Cloud Platform interface.
Manually creating two remotes for your local repository clone: one at GitHub or Bitbucket, and one at Cloud Platform.
Using GitHub with Cloud Platform
The first step is to create two remote repositories. Suppose you have an existing repository at GitHub containing your application’s code. Use the following commands to make a local clone:
GitHub is the origin remote, the default location for gitpush and gitpull.
To deploy this code to Cloud Platform, add your Cloud Platform repository as an additional remote, named something short, like ac, and then do an initial gitpush--forceac to reinitialize the Cloud Platform repository. You can find the URL of your Cloud Platform repository in the Cloud Platform interface, using Application info panel.
Now you have two remotes, origin (GitHub) and ac (Cloud Platform).
Pushing changes
After you have set up your two remote repositories, keep them in sync by pushing local changes to both GitHub and Cloud Platform. You can edit some files and push them to GitHub:
You can also push the same changes to Cloud Platform:
git push ac master
Your new code is now in both your GitHub and Cloud Platform repositories and is running on your Cloud Platform application.
Synchronizing release tags
Suppose that now you deploy your code on Cloud Platform from the Development environment (running the master branch) to Production. This creates a new release tag in your Cloud Platform repository that shows you exactly what code you deployed that day. You do not have to synchronize that release tag to GitHub, but you can:
git pull ac
From svn-18.devcloud.hosting.acquia.com:mysite
* [new tag] 2012-03-12 -> 2012-03-12
git push --tags
Now your GitHub repository contains the same release tag as your Cloud Platform repository.
Translating your root directory with git subtree
Cloud Platform requires that you keep all of your Drupal application code in the directory docroot in your repository. Your existing GitHub repository may not be set up that way, and you may have a lot of commit history in that repository that you want to preserve. To preserve your GitHub repository’s directory structure and commit history, you can use gitsubtree to translate your GitHub repository’s root directory into a Cloud Platform docroot directory.
Using BitBucket with Cloud Platform
Here is how to make your Cloud Platform code repository available on Bitbucket as well:
Create an account on bitbucket.org. Bitbucket offers unlimited private repositories for free for up to five users. During the account creation process, select the empty repository option and provide it with a name.
Once your account has been created and your empty repository is provisioned, add your SSH public key to Bitbucket under your account settings. You can either use an existing key or generate a new key pair for Bitbucket use only.
On your Bitbucket repository overview page, under Command line, click I have an existing project and copy the remote URL, which should appear similar to the following:
On your local command line, navigate to your Cloud Platform repository directory and run the following to add a new remote named bitbucket. Of course, you’ll need to replace the git@bitbucket location with the actual one you copied from your repository overview page; you can also name the new remote whatever you’d like:
Push all of your code, including branches and tags, to your new Bitbucket remote repository:
git push -u bitbucket --all
When prompted for a password, which is only necessary the first time you connect, enter your actual Bitbucket account password before you proceed with the push.
When you refresh your repository overview on Bitbucket, you should now see all of your code and commits.
If you want to keep your Cloud Platform and Bitbucket repositories in sync, create a new alias named all in the .git/config file in your repository:
You can find the URL of your Cloud Platform repository in the Cloud Platform interface’, using the Application info panel.
When you push new commits, use the all alias to push simultaneously code to both Cloud Platform and Bitbucket:
git push all
Connecting to JIRA
JIRA is Atlassian’s issue tracking and project management software. For information about how to connect your remote Bitbucket or GitHub repository to JIRA, see Atlassian’s documentation.
Cloud Platform