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.

Travis CI skip conditions

See original GitHub issue

Recently the Travis CI queue has taken a bit of a beating. This has been caused by large demand. The small number of workers (appears to 164) quickly getting maxed out. Some unfortunate multi-day infrastructure issues that left jobs hanging. This has led me to wonder what improvements we can make in this area. The big wins unfortunately will require a significant amount of discussion and work. Though there are still some simple small wins that should improve on the situation.

Awhile back we added PRs ( https://github.com/conda-forge/conda-smithy/pull/87 ) ( https://github.com/conda-forge/conda-smithy/pull/94 ) which eliminated the appveyor.yaml file when it wasn’t needed. Subsequently @pelson put forward PR ( https://github.com/conda-forge/conda-smithy/pull/95 ), which pushed a button on AppVeyor to disable builds when appveyor.yaml wasn’t present. This saved a significant number of builds on AppVeyor and made that queue very usable for us.

We can use this same strategy with Travis CI. It also has a toggle switch that can be set via the Travis CI API as stated in the docs. Also, we can use the same logic to rename the .travis.yml file. All of this should only be a handful of lines of code. While this isn’t a huge win, it is easy to do and does help some.

Issue Analytics

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

Top GitHub Comments

1reaction

jakirkhamcommented, Jul 11, 2016

So, I think there are ~25 feedstocks that have benefited from these improvements and skipping CircleCI builds via PR ( https://github.com/conda-forge/conda-smithy/pull/218 ). Again this isn’t huge when looking at the nearly 800 feedstocks present. Still it isn’t such a small number either. After all with CI usage the question is less about how many feedstocks and more about how many active feedstocks. Thus ~25 feedstocks ends up being a more significant number.

1reaction

pelsoncommented, Jul 1, 2016

Thanks for this detail @jakirkham. FWIW, I’m available for a good few hours now to work on these issues. Ping me if you need anything.

Top Results From Across the Web

Conditions - Travis CI Docs

Conditions can be used to filter out, and reject builds, stages, jobs, and notifications by specifying conditions in your build configuration (your ....

Skip travis build if certain condition is met

Basically what I'm trying to do here is skip the entire build pipeline if certain condition is met. That condition is, “if files...

How to skip making a build in Travis-ci (Example) - Coderwall

Travis -Ci a has nice feature which allows to skip making a build for certain push. Just add [ci skip] into your commit's...

Add a [skip travis] command · Issue #5032 - GitHub

It should be possible to stop tests by adding a bash condition at the beginning of the Travis CI build, in order to...

Travis CI skip test and deploy - continuous integration

You can add a script with a echo to your .travis.yml file. This will force Travis to run your script message instead of...