Open ghost opened 7 years ago
Add a pod lib lint test to the CI script to ensure that the pod stays valid on all targets in the podspec.
pod lib lint
This could either be done after the Xcodebuild test script using the command above or, if you want to also migrate to Fastlane, you could use the pod_lib_lint command in the Fastfile (see https://github.com/ustwo/formvalidator-swift/blob/master/fastlane/Fastfile as an example).
pod_lib_lint
In either case, a Gemfile with CocoaPods in it should also be added to ensure a pinned version of CocoaPods is used for the linting.
For more detail on linting a Pod see: https://guides.cocoapods.org/terminal/commands.html#pod_lib_lint
Nice one. I was also thinking about a way to automate this test. Thanks for sharing and raising!
Summary
Add a
pod lib lint
test to the CI script to ensure that the pod stays valid on all targets in the podspec.Details
This could either be done after the Xcodebuild test script using the command above or, if you want to also migrate to Fastlane, you could use the
pod_lib_lint
command in the Fastfile (see https://github.com/ustwo/formvalidator-swift/blob/master/fastlane/Fastfile as an example).In either case, a Gemfile with CocoaPods in it should also be added to ensure a pinned version of CocoaPods is used for the linting.
Notes
For more detail on linting a Pod see: https://guides.cocoapods.org/terminal/commands.html#pod_lib_lint