CircleCI: Use --include-podspecs when validating WordPress-Editor-iOS podspec to avoid publishing problems #1220
Conversation
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 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 requires wordpress-mobile/circleci-orbs#40 to be merged.
We have a problem with the CocoaPod publishing workflow for Aztec-iOS.
WordPress-Aztec-iOS.podspecis a dependency ofWordPress-Editor-iOS.podspec. This means that when the version numbers in the podspecs are bumped prior to making a new release, CI fails to validateWordPress-Editor-iOS.podspecbecause it can't find the new version ofWordPress-Aztec-iOS.The solution is to make use of a reasonably recent addition to CocoaPods (CocoaPods/CocoaPods#8536) which allows us to include local podspecs during validation and avoid searching the specs repo for
WordPress-Aztec-iOS.To test:
CI
Test locally
WordPress-Aztec-iOS.podspecandWordPress-Editor-iOS.podspecto something not yet released (e.g.1.2.0) but don't commit your changes.bundle exec pod lib lint WordPress-Editor-iOS.podspec --include-podspecs=WordPress-Aztec-iOS.podspecand see that validation passes even though this version isn't released yet.