Migrating from Azure DevOps
This document provides an overview of how to migrate from Azure DevOps to CircleCI.
|Tips provided by ImagineX Consulting|
Source Control Setup
If you are using Azure DevOps Git or TFVC repositories, you will first need to migrate your source code to GitHub or BitBucket. For Azure DevOps Git repos, here are links on how to import into GitHub or BitBucket:
For TFVC repositories, we recommend using the git-tfs tool. Here’s a link to the tool and steps for using it:
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
If you need to export other Azure DevOps artifacts, you can download most of the data into Excel spreadsheets. Follow the Azure DevOps documentation on saving project data.
Once you have imported your code into GitHub or BitBucket, you can start creating a project in CircleCI using the Getting Started guide.
If you’re using Azure DevOps Pipelines or TFS Build and Release, you’ll need to migrate your build configuration. In Azure DevOps Pipelines, the build configuration is defined in a file called
azure-pipelines.yml in the root directory of your source code repository. In TFS Build and Release, the build configuration is done through the web interface and can be exported to a json file. In either case, 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 Azure DevOps Pipelines and CircleCI configurations will be different. It may be helpful to have both Azure 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 in concurrently. Once they’re done, Job3 runs. Once Job3 is done, Job4 runs.
| || |
Execute jobs on multiple platforms. Azure DevOps uses pools and demands to identify build runners. CircleCI provides executors for docker, Linux and MacOS.
| || |
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 guide first).
- 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.