# Using build matrix for custom stage

**URL:** <https://travis-ci.community/t/using-build-matrix-for-custom-stage/3456>\
**Category:** Uncategorized\
**Created:** [May 20, 2019, 3:38pm UTC](https://travis-ci.community/t/using-build-matrix-for-custom-stage/3456 "2019-05-20T15:38:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 20, 2019, 8:03pm UTC](https://travis-ci.community/t/using-build-matrix-for-custom-stage/3456/2 "2019-05-20T20:03:45Z")

</div>

As per [Trouble with Python build matrix being respected by jobs](https://travis-ci.community/t/trouble-with-python-build-matrix-being-respected-by-jobs/3432/2) , stages are not considered an axis so you cannot use the matrix to add jobs to more than one stage.

Maybe you can specify `stage` at top level to change the name of the default stage.

---

_[View the full topic](https://travis-ci.community/t/using-build-matrix-for-custom-stage/3456)._