Split Travis builds by Python version #822
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We previously had all python versions of our packages building on a single job, this PR proposes to split up the python versions to separate jobs on Travis. [The dev repo](omnia-md/conda-dev-recipes#81) has had this feature for a while now and I think its worth considering for here. There are up and downsides so I would like some feedback and opinions. Pros: * Reduces odds of a timeout due to multiple versions being built in the same job * Easier debugging of specific versions * Likely faster total build times in linux and *maybe OSX* Cons: * Adds more jobs which must run, jobs may delay each other since Travis has a concurrent job limit * Each job has to pull down the docker image, slower cumulative start time, but can be done in parallel so wall clock will be faster (limited by previous point) * OSX Builds may actually take longer in Wall Clock time because Travis OSX builds are often backlogged due to total global requests. Thoughts and opinions?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We previously had all python versions of our packages building on a single job, this PR proposes to split up the python versions to separate jobs on Travis. The dev repo has had this feature for a while now and I think its worth considering for here. There are up and downsides so I would like some feedback and opinions.
Pros:
Cons:
Thoughts and opinions?