Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TST: Use Travis CI build stages?

See original GitHub issue

Are you interested in this new Travis CI feature? See https://docs.travis-ci.com/user/build-stages/ for info and see https://travis-ci.org/astropy/astropy for the feature as used by astropy.

The motivation to use this is when you don’t want bother with running the rest of the builds if some important ones fail. However, this also adds to total testing time, because subsequent stages are not started until the earlier ones pass.

Please close this issue if you are not interested.

Issue Analytics

State:
Created 6 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

ejeschkecommented, Oct 31, 2017

@pllim, I haven’t yet had time to take at look at this. Will do so soon.

0reactions

pllimcommented, Oct 31, 2017

Top Results From Across the Web

Build Stages - Travis CI Docs

Build stages is a way to group jobs, and run jobs in each stage in parallel, but run one stage after another sequentially....

Build Stages: Defining different steps on different stages

This example has 2 build stages: Two jobs that run different suites of tests against Ruby 2.3.1; One job that runs a custom...

Job Lifecycle - Travis CI Docs

Each job is a sequence of phases. The main phases are: ... Travis CI can run custom commands in the phases: ... There...

Build Stages: Matrix expansion - Travis CI Docs

Build Stages : Matrix expansion. This example has 2 build stages: Four test jobs that have been expanded from rvm and env matrix...

Customizing the Build - Travis CI Docs

Builds on Travis CI are configured mostly through the build configuration stored in the file .travis.yml in your repository. This allows your configuration...