Since our introduction of pipelines and v2.1 config, our team has been working on shipping features that make CircleCI more configurable, more flexible, and more efficient. Some of the additions we’ve made are orbs, reusable config, pipeline variables, and a new UI that makes viewing status and fixing builds more efficient than ever. Matrix jobs are our latest enhancement to this set of features.
What are matrix jobs?
Matrix jobs are a developer’s secret weapon to write simple configuration for complicated software. With only a few lines of config, you can go from a single test to a more comprehensive test suite, or from one task into a parallelized batch of related work. We’re excited to announce that CircleCI now has support for matrices as part of our workflow syntax. Our matrix implementation works in tandem with our existing support for parameterized jobs, putting it in a unique position to serve a wide variety of use cases.
So how do we express this in CircleCI? First we’ll define two executors representing the operating systems we want to test on. Then, we must create a parameterized job, called test, whose parameters match the dimensions of the matrix.
version: 2.1 executors: linux: docker: - image: cimg/base:2020.01 macos: macos: xcode: 11.4 orbs: node: firstname.lastname@example.org jobs: test: parameters: os: type: executor node-version: type: string executor: << parameters.os >> steps: - checkout - node/install: node-version: << parameters.node-version >> install-yarn: true - run: yarn test
Finally, we’ll create a workflow that invokes this job using a matrix:
workflows: all-tests: jobs: - test: matrix: parameters: os: [linux, macos] node-version: ["10.9.0", "11.9.0", "12.9.1", "13.9.0"]
Pushing this config and examining my pipeline result shows me that I’ve indeed created a workflow of 8 jobs that covers all the bases:
For another look at setting up and running matrix jobs, check out the video below.
Matrix jobs are now available to all CircleCI users. This feature is powerful because it works with any combination of job parameters, generating human-readable names for each individual job. You aren’t restricted to a finite number of ways to do cross-platform testing such as just the Node.js version and operating system. It can be anything representable as a job parameter. The docs include even more advanced features such as excluding specific combinations and using templated dependencies to create complex workflows.
To learn more about the other features mentioned in this post, see the links below: