Migrate from Travis to Azure Pipelines #111
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
Codecov Report
@@ Coverage Diff @@
## master #111 +/- ##
=======================================
Coverage 76.21% 76.21%
=======================================
Files 38 38
Lines 2052 2052
=======================================
Hits 1564 1564
Misses 488 488Continue to review full report at Codecov.
|
arjungupta0107
pushed a commit
to salido/XMLCoder
that referenced
this pull request
Jun 26, 2020
Unfortunately, Travis seems to be very slow and unreliable compared to Azure Pipeline builds. I've already migrated a few other OSS projects to Azure and it worked pretty great. The only thing we lose for now is binary frameworks built with Carthage attached to release assets. I don't think this is a blocker, since with the imminent release of Xcode 11 I anticipate usage of Carthage to decrease with more people migrating to SwiftPM. In addition, there's a stronger demand now for a SwiftPM binary frameworks proposal, and these scripts would have to be changed anyway to support the new XCFrameworks. Azure Pipelines does not prevent us from doing that, I'd just like to wait until all that stuff is stable enough before we start integrating this into our CI process. * Add azure-pipelines.yml and related scripts * Remove unused `carthage bootstrap` command * Remove .travis.yml
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.
Unfortunately, Travis seems to be very slow and unreliable compared to Azure Pipeline builds. I've already migrated a few other OSS projects to Azure and it worked pretty great. The only thing we lose for now is binary frameworks built with Carthage attached to release assets. I don't think this is a blocker, since with the imminent release of Xcode 11 I anticipate usage of Carthage to decrease with more people migrating to SwiftPM. In addition, there's a stronger demand now for a SwiftPM binary frameworks proposal, and these scripts would have to be changed anyway to support the new XCFrameworks. Azure Pipelines does not prevent us from doing that, I'd just like to wait until all that stuff is stable enough before we start integrating this into our CI process.