Allow build children to run #5881
Merged
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
This was a regression from the moving of the file
|
Where do OSX builds run? Not on Travis? |
|
You can only build one type of travis jobs in one script. This triggers another travis job that does the osx build |
|
That's not true; you can specify the |
|
Ok, I didn't know that it's probably worth investigating to port our jobs to run OSX in the same job. Never the less this was originally setup to trigger a child job (not by me) to run on OSX and as as far as I know that was because there was no support for running mixed OS jobs at that time. |
|
In any case, I don't think anything could go wrong here. |
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.
This was a regression from the moving of the file which resulted in the launching of the OSX builds to fail. This only applies on the master branch since the 2.x and 1.5.x branch don't have this issue