Deprecate Travis CI in favor of Azure #5659
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
Port the linter job from Travis CI into Azure. This is a 1-1 port. Signed-off-by: Filip Jeremic <[email protected]>
Travis CI linter was the only job that we ran. Deprecate it in favour of Azure. Signed-off-by: Filip Jeremic <[email protected]>
Signed-off-by: Filip Jeremic <[email protected]>
fjeremic
requested review from
0xdaryl,
charliegracie,
Leonardo2718 and
mstoodle
as code owners
0xdaryl
approved these changes
Nov 9, 2020
There was a problem hiding this comment.
Looks good to me. Thanks @fjeremic for taking care of this.
I will merge later today in case there are comments from any other reviewers before then.
@AdamBrousseau FYI.
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.
Migrate the linter job from Travis CI to Azure and remove remanence of Travis CI documentation in the repository. We also take this opportunity to refresh to Azure ccache since we have not done so in a while.
Issue: #5571