Information for: DEVELOPERS   PARTNERS

Using Acquia Cloud with a remote repository

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 Acquia Cloud:

  • The Acquia Cloud pipelines feature, which provides integration with GitHub, Bitbucket, and the Acquia Cloud interface.
  • Manually creating two remotes for your local repository clone: one at GitHub or Bitbucket, and one at Acquia Cloud.

Using GitHub with Acquia Cloud

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:

git clone [email protected]:me/mysite.git
cd mysite
git remote -v
origin  [email protected]:me/mysite.git (fetch)
origin  [email protected]:me/mysite.git (push)

GitHub is the origin remote, the default location for git push and git pull.

To deploy this code to Acquia Cloud, add your Acquia Cloud repository as an additional remote, named something short, like ac, and then do an initial git push --force ac to reinitialize the Acquia Cloud repository. You can find the URL of your Acquia Cloud repository in the Acquia Cloud interface, using Application info panel.

git remote add ac [email protected]:mysite.git
git remote -v
origin  [email protected]:me/mysite.git (fetch)
origin  [email protected]:me/mysite.git (push)
ac  [email protected]:mysite.git (fetch)
ac  [email protected]:mysite.git (push)
git push --force ac

Now you have two remotes, origin (GitHub) and ac (Acquia Cloud).

Pushing changes

After you have set up your two remote repositories, keep them in sync by pushing local changes to both GitHub and Acquia Cloud. You can edit some files and push them to GitHub:

vi somefile.php
git add somefile.php
git commit -m 'edited somefile.php'
git push origin master

You can also push the same changes to Acquia Cloud:

git push ac master

Your new code is now in both your GitHub and Acquia Cloud repositories and is running on your Acquia Cloud application.

Learn more about cloning your Acquia Git repository and pushing local changes your by visiting the Acquia Academy (sign-in required) for the Git Fundamentals for Acquia Cloud video tutorial.

Synchronizing release tags

Suppose that now you deploy your code on Acquia Cloud from the Development environment (running the master branch) to Production. This creates a new release tag in your Acquia Cloud 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
* [new tag]  2012-03-12 -> 2012-03-12
git push --tags

Now your GitHub repository contains the same release tag as your Acquia Cloud repository.

Translating your root directory with git subtree

Acquia Cloud 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 git subtree to translate your GitHub repository’s root directory into an Acquia Cloud docroot directory.

Using BitBucket with Acquia Cloud

Here is how to make your Acquia Cloud code repository available on Bitbucket as well:

  1. Create an account on 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.

  2. 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.

  3. 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:

    [email protected]:[username]/[repo].git
  4. On your local command line, navigate to your Acquia Cloud 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:

    git remote add bitbucket [email protected]:[username]/[repo].git
  5. 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.

  6. When you refresh your repository overview on Bitbucket, you should now see all of your code and commits.

If you want to keep your Acquia Cloud and Bitbucket repositories in sync, create a new alias named all in the .git/config file in your repository:

[remote "all"]
    url = [sitename]@svn-[number][sitename].git
    url = [email protected]:[username]/[repo].git

You can find the URL of your Acquia Cloud repository in the Acquia Cloud interface’, using the Application info panel.

When you push new commits, use the all alias to push simultaneously code to both Acquia Cloud 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.