# Matrix and normal jobs combined

**URL:** <https://travis-ci.community/t/matrix-and-normal-jobs-combined/10233>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** build-stages, travis-yml, build-matrix\
**Created:** [October 21, 2020, 3:39pm UTC](https://travis-ci.community/t/matrix-and-normal-jobs-combined/10233 "2020-10-21T15:39:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seluj78](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/seluj78/32/861_2.png) [@Seluj78](https://travis-ci.community/u/Seluj78)\
**Post date:** [October 21, 2020, 3:39pm UTC](https://travis-ci.community/t/matrix-and-normal-jobs-combined/10233/1 "2020-10-21T15:39:52Z")

</div>

![Screenshot 2020-10-21 at 17.38.31](https://us1.discourse-cdn.com/flex015/uploads/travis_ci/original/2X/9/9eac2694fd54cd0ead85c07bdec3373ec981a445.png)

As you can see in the screenshots, I have three build stages that are required before running the tests and linting. Is it possible to use a matrix for the builds and then run the tests then the linting ?

Here’s the travis-ci for the project: [https://github.com/Seluj78/PyMatcha/blob/dev/.travis.yml](https://github.com/Seluj78/PyMatcha/blob/dev/.travis.yml)

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [October 21, 2020, 11:11pm UTC](https://travis-ci.community/t/matrix-and-normal-jobs-combined/10233/3 "2020-10-21T23:11:19Z")

</div>

Build matrtix only adds jobs to the default stage. You can customize that stage’s name by specifying `stage:` at top level.

Example: [https://travis-ci.com/github/native-api/test\_travis/builds/191514084](https://travis-ci.com/github/native-api/test_travis/builds/191514084)

So using just the matrix will only work for you if the jobs in question can run in parallel.

* * *

If you want multiple similar jobs in different stages, you can save on duplication by

- defining the shared parts at global level
- using [YAML anchors](https://yaml.org/spec/1.1/#id899912)
