Running your Travis CI builds locally with Docker

Setting up the ecosystem to run the exams on a CI/CD can acquire a several roundtrips involving your host device and the CI/CD functioning remotely. For each individual try, you’ll have to commit and publish your alterations prior to waiting for the CI/CD system to choose up the most up-to-date model of your code, initialize the environment this kind of as downloading and setting up the dependencies, and ultimately operate the tests.

With Travis CI and a small of perform, you can recreate the ailments of your exams by downloading and recreating the Docker graphic which Travis CI is using. This is a tiny innovative subject matter which will come in useful when your assessments are a tiny far more sophisticated than regular.

Ahead of beginning, your job ought to presently be on GitHub and activated in Travis CI. At the very least a single construct ought to have been executed. We use the develop log to extract the Docker picture to use as effectively as the instructions executed by Travis CI inside of the container to put together the career. In the Career log of your task, develop the Worker information and facts line and search for the line starting with occasion:.

Worker facts
hostname: bda7cfb4-248b-4402-aa9f-291eaca299e5@1.worker-org-cfdfb76bd-fv5jt.gce-output-4
edition: v6.2.20-1-g3a987d6 https://github.com/travis-ci/worker/tree/3a987d61ed169c9539advert435d1a9b5f2d8c6ce4a6
instance: travis-occupation-8c5d2a02-68a2-4b51-bc02-625ef2c37ad3 travis-ci-sardonyx-xenial-1593004276-4d46c6b3 (by way of amqp)startup: 5.913615831s

The title of the Docker image is the phrase following travis-ci-, sardonyx in the instance higher than. From there, go to the Docker registry of Travis CI, localize the suitable Docker image, travisci/ci-sardonyx in my circumstance, and extract the newest model in the tags segment. It is packer-1606895335-7957c7a9 for me.

Now, update the command beneath with the title of the Docker image:

Occasion="travisci/ci-sardonyx:packer-1606895335-7957c7a9"

You can now start out the container and enter within:

BUILDID="construct-$RANDOM"
docker operate --title $BUILDID -dit $Instance /sbin/init
docker exec -it $BUILDID bash -l

At the time you enter into the container, login with the travis user and put in the offers using the Travis CI logs as an illustration:

su - travis
git clone --depth=50 --department=learn https://github.com/adaltas/remark-gatsby-plugins.git adaltas/remark-gatsby-plugins
cd adaltas/remark-gatsby-plugins
git checkout master
nvm install 14
yarn --frozen-lockfile
yarn test
yarn run v1.22.5
$ lerna operate test
lerna detect cli v3.22.1
lerna data versioning impartial
lerna facts ci enabled
lerna information Executing command in 1 package deal: "yarn operate test"
lerna details operate Ran npm script 'test' in 'gatsby-remark-title-to-frontmatter' in 1.2s:
$ mocha 'test/**/*.coffee'
  Extract title
    ✓ Go the title to frontmatter
  1 passing (21ms)
lerna results operate Ran npm script 'test' in 1 package in 1.2s:
lerna achievements - gatsby-remark-title-to-frontmatter
Completed in 1.95s.

If the tests are productive domestically on your Docker picture, odds are that they will go remotely on the Travis CI system.