This repository was archived by the owner on Apr 15, 2026. It is now read-only.
DISPATCH-1115: make TravisCI job use a Proton release in addition to master#428
Closed
gemmellr wants to merge 1 commit into
Closed
DISPATCH-1115: make TravisCI job use a Proton release in addition to master#428gemmellr wants to merge 1 commit into
gemmellr wants to merge 1 commit into
Conversation
Member
Author
|
Ignore this comment (but not the PR), testing integration. |
Member
Author
|
Ignore this comment (but not the PR), testing integration again. |
Member
Author
|
Updated to only do the coverage build and reporting tasks on one of the sub-jobs |
Member
Author
|
Pushed this as it seems to work as desired, if folks have other improvements we can add them later. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There have been various cases that using only Proton master for CI caused Dispatch test failures, or lead to Dispatch master only working with proton master when this wasn't particularly desired at the time. This can cause wasted time when investigating test failures, and complicate release cycles / compatibility unnecessarily.
This change swaps to getting Proton from a checkout rather than submodule, and makes the proton version an env variable forming a matrix of sub-jobs to test different versions, such as master and last release as currently used here.