Migrate from AWS
On This Page
This document provides an overview of how to migrate from AWS CodeCommit to CircleCI.
|Tips provided by ImagineX Consulting|
Source control setup
If you are using AWS Code Commit, you will first need to migrate your source code to GitHub or Bitbucket. See the following for details on how to import your code:
Following are the steps required for using the git command line tool to import your code into GitHub Enterprise:
Create an empty repository on your GitHub Enterprise instance.
Create a bare clone of your external repository on your local machine, fetching all remote tags (refs/tags/*) and copying all remote branch heads (refs/heads/\*) directly to their corresponding local branch heads.
git clone https://external-host.com/extuser/repo.git --bare
Add your GitHub Enterprise repository as a remote reference in your local clone.
cd [repo-name] git remote add enterprise git@[hostname]:[owner]/[repo-name].git
Push all local references (refs/*) up to your remote GitHub Enterprise repository.
git push enterprise --mirror
Once you have imported your code into GitHub or Bitbucket, you can start creating a project in CircleCI using the Getting Started guide.
Next, you will need to migrate your build configuration. On AWS CodeBuild, the build configuration is either defined in the web interface or in a file called
buildspec.yml in the root directory of your source code repository. If you use shell scripts to perform your build, you can reuse those scripts in CircleCI.
First, create a CircleCI build configuration file. In the root directory of your source code repository, create a folder named
.circleci and create a file in that folder named
config.yml. Next, follow the CircleCI documentation here to learn how to configure the
The AWS CodeBuild and CircleCI configurations will be different. It may be helpful to have both AWS DevOps and CircleCI reference documentation open side-by-side to help with the conversion of the build steps:
Define a job that executes a single build step.
Specify a docker image to use for a job.
Define a multi-stage build pipeline. Job1 and Job2 run concurrently. Once they are done, Job3 runs. Once Job3 is done, Job4 runs. An AWS CodeBuild project runs all commands sequentially. If you are running concurrent commands, you are probably using CodePipeline and multiple CodeBuild projects.
Execute jobs on multiple platforms. An AWS CodePipeline project can target a single platform only. If you are targeting multiple platforms, you’re probably using CodePipeline and multiple CodeBuild projects. CircleCI provides executors for docker, Linux and MacOS that can be combined in a single build definition.
For larger and more complex build files, we recommend moving over the build steps in phases until you get comfortable with the CircleCI platform. We recommend this order:
Help make this document better
This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guidefirst).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.
You can also visit our support site to find support articles, community forums, and training resources.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.