As a Senior Success Engineer, I’ve been helping many of our customers migrate their projects from CircleCI 1.0 to 2.0 over the past few months. And after migrating hundreds of projects, I know the most common places teams run into issues. In this blog post, I’ve collected the tips I’ve shared most often with customers while migrating their projects to CircleCI 2.0, and some gotchas to look out for along the way. Happy migrating!

Test CircleCI 2.0 incrementally

Did you know you can build the same project on both CircleCI 1.0 and 2.0? When starting to migrate to CircleCI 2.0 you don’t have to go all in right away. To keep your project building on 1.0 and test out 2.0, try this:

  • Create a new branch for testing CircleCI 2.0.
  • Remove circle.yml from that branch and add a .circleci/config.yml file.
  • Write some minimal 2.0 config on that branch and push it until you get a green build.
  • We recommend doing a little bit of config at a time so you can get feel for how it works. Initially, just check out the code, then try installing dependencies, then try running your tests. Later, you can start working out how to cache dependencies and use more advanced features like Workflows. Build up your config bit by bit.
  • When you have everything working, you can merge the branch with the new config into your main project.

CircleCI 2.0 quick tips

  • Commands listed in the steps can only be run in the first container listed in the docker section.
  • Run builds frequently to test the config thus far. If something breaks, you know what changed since the last build.
  • Don’t add Workflows initially; wait until you have a functional build.
  • Build a config manually from scratch, but use the config-translation endpoint as a reference.
  • You can’t define env vars with env vars in the environment section of the config.
    • The workaround is to echo the vars into $BASH_ENV
      • This only works with bash, not sh (Alpine images only have sh)
  • Conditionally run commands with bash if statements.
    • if [ $CIRCLE_BRANCH = “master” ] ; then ./ci.sh ; fi
  • Conditionally halt the build at that step with circleci step halt
    • Allows you to use setup_remote_docker conditionally by halting
  • The Timezone can be changed just by defining an env var.
    • TZ: “/usr/share/zoneinfo/America/New_York”
  • Running the build out of /dev/shm (ie., /dev/shm/project) can speed up certain projects.
    • Some things like Ruby gems can’t be loaded out of shared memory. They can be intalled elsewhere in the system (~/vendor) and symlinked in.
  • Instead of prefixing a lot of commands with sudo, consider setting the shell to sudo for that run.
    • shell: sudo bash -eo pipefail
  • Docker builds and docker-compose should generally be run in the machine unless language-specific tools (Ruby, Node, PHP, etc.) are required beforehand, then the remote environment is sufficient.
  • Some tasks can be set to run in the background to save overall build time, but be careful of running out of resources.
  • Different resource_class sizes can be beneficial and it’s worth trying them to see their impact. It could have no impact at all.
  • The $PATH can be set to a string. If you don’t know your Docker image’s $PATH, just run it and echo $PATH or take a look at the output of env.
  • The sha of an image can be referenced under the Spin up Environment step. An image can be hardcoded to that sha value to make it immutable.
  • Service containers can be run with custom flags.
    • command: [mysqld, –character-set-server=utf8mb4, –collation-server=utf8mb4_unicode_ci, –init-connect=’SET NAMES utf8mb4;’]
  • Configure your test runners to only spawn two threads/workers (or more if you’re using resource_class) when running in CI. Sometimes they will optimize themselves based on incorrect values. Check out this video with more info.

Migration tips: 1.0 –> 2.0

  • Note that $CIRCLE_ARTIFACTS and $CIRCLE_TEST_REPORTS are not defined in 2.0.
    • You can define them yourself, but be sure to mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS if you do.
  • Migrating Linux & macOS in one repository (like React Native) should involve opening one branch for each Linux & macOS before combining the two configs into one workflow.
  • You can’t sudo echo - pipe it like this: echo “192.168.44.44 git.example.com” sudo tee -a /etc/hosts`
  • Fonts are different between Ubuntu and Debian systems.
  • Apache 2.2 and 2.4 configs are fairly different - make sure to upgrade your 2.2 configs.
  • Don’t forget all the commands inferred automatically by 1.0 and commands manually stored in the UI.

Language-specific tips

Python

  • Typically expects classnames and not filenames to run tests

Ruby

  • Ruby files can load in a different order than expected on AUFS
  • Define $RAILS_ENV and $RACK_ENV as test (this was automatic in 1.0)

Java(-based)

  • Java (apps, tools, and services) will OOM (run out of memory) because it doesn’t recognize how much RAM is available. An environment variable should be defined. If it’s still OOMing, a bigger container is necessary.
    • https://circleci.com/blog/how-to-handle-java-oom-errors/
  • Scala projects can have filenames that are too long, include the -Xmax-classfile-name flag.
    • https://discuss.circleci.com/t/scala-sbt-assembly-does-not-work/10499/10 scalacOptions ++= Seq( “-encoding”, “utf-8”, “-target:jvm-1.8”, “-deprecation”, “-unchecked”, “-Xlint”, “-feature”, “-Xmax-classfile-name”, “242” <= add here ),

Browser testing tips

  • Tests can sometimes be flaky and fail for seemingly no reason. Some people opt to re-run their failing browser tests automatically. The drawback is corrupting the timing data.
  • Take screenshots of failed tests to make debugging easier.
  • VNC can be installed & used. The browser can be dragged around in VNC after installing metacity. Run this from one of our browsers images: ssh -p PORT ubuntu@IP_ADDRESS -L 5902:localhost:5901 # To connect via SSH sudo apt install vnc4server metacity vnc4server -geometry 1280x1024 -depth 24 export DISPLAY=:1.0 metacity & firefox &

Docker-specific tips

  • Build a Docker image on a cron job.
    • Build weekly, daily, or whenever you need.
      • It’s possible to trigger a new Docker image build via the API easily
    • Include dependencies like node_modules in the image.
      • They help mitigate issues from a DNS outage.
      • They keep the dependencies version controlled.
      • Even if a module disappears from node’s repos, the necessary depenencies to run the application are safe.
    • A private image can include private gems and private source cache.
  • There is no socket file for databases so the host variables need to be defined ($PGHOST, $MYSQL_HOST) to specify 127.0.0.1, forcing TCP.
  • Using CircleCI convenience or official Docker Hub images increases the chance of having your image cached on the host.
    • Building off these images will reduce the number of image layers that need to be downloaded.
  • Using the -ram variation of a container will run the given daemon in /dev/shm.
  • Building custom images with everything pre-installed speeds up the build and adds reliability.
    • Heroku (as an example) could push a bad update to their installer, breaking your builds.
  • The dockerize utility can be used to wait for service containers to be available before running tests.
    • https://github.com/jwilder/dockerize
  • ElasticSearch has their own Docker registry from which to pull.
    • https://www.docker.elastic.co/
  • Containers can have names so multiple of a given service can run on the same port with different hostnames.
  • Privileged containers can be run in the remote environment and the machine.
  • Volumes can’t be mounted from the base Docker executor into the remote environment.
    • docker cp can transfer files.
    • Volumes referenced will be mounted from the within the remote environment into the container.

For more information about migrating to CircleCI 2.0, see our documentation. If you need additional help, please visit our support page.