Switch from matrix to build stages

[cotsog]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 136

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.536%

---

Totals
Change from base Build 134:	0.0%
Covered Lines:	283
Relevant Lines:	284

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 136

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.536%

---

Totals
Change from base Build 134:	0.0%
Covered Lines:	283
Relevant Lines:	284

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 136

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.536%

---

Totals
Change from base Build 134:	0.0%
Covered Lines:	283
Relevant Lines:	284

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 138

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.536%

---

Totals
Change from base Build 134:	0.0%
Covered Lines:	283
Relevant Lines:	284

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 136

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.536%

---

Totals
Change from base Build 134:	0.0%
Covered Lines:	283
Relevant Lines:	284

---

💛 - Coveralls

[JamesMessinger]

Any particular reason for this? As far as I can tell, it accomplishes the same task, but slower, since each stage runs sequentially

[cotsog]

My bad for the first commit.

In the end you need to make sure to override the node_js and os keys in your Deploy stage.

See https://docs.travis-ci.com/user/build-stages/matrix-expansion/.

[JamesMessinger]

It's unnecessary to set the node_js and os keys in the "Deploy" stage because they are automatically inherited from the build matrix.

See https://docs.travis-ci.com/user/build-stages/#build-stages-and-build-matrix-expansion

[cotsog]

It seems my assumptions were wrong. I wrongfully thought that you would need to define the os and node_js keys in you deploy stage in order for the resulting job to be recognized as a different stage. However, I did some tests with and without the keys being defined and I could not reproduce your issue. I'm following up with you via e-mail. Thanks!