Skip to content
This repository was archived by the owner on Mar 7, 2025. It is now read-only.

iOS: Add Slack notifications and safety checks to publish-podspec#38

Merged
jtreanor merged 1 commit intomasterfrom
cocoapods-trunk-updates
Oct 3, 2019
Merged

iOS: Add Slack notifications and safety checks to publish-podspec#38
jtreanor merged 1 commit intomasterfrom
cocoapods-trunk-updates

Conversation

@jtreanor
Copy link
Copy Markdown
Contributor

@jtreanor jtreanor commented Oct 2, 2019

We have now been using this command successfully with WordPressAuthenticator for a few weeks. This adds a few minor improvements before I start rolling it out more widely:

  • It ensures the $CIRCLE_TAG matches the version in the podspec.
  • Optionally post a success message to Slack.

You can see it working here.

@jtreanor jtreanor requested a review from jkmassel October 2, 2019 15:51
Copy link
Copy Markdown
Contributor

@jkmassel jkmassel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the example isn't passing:

warning: Capabilities for Signing & Capabilities may not function correctly
because its entitlements use a placeholder team ID. To resolve this, select
a development team in the App editor. (in target 'App' from project 'App')

warning: Skipping code signing because the target does not have an
Info.plist file and one is not being generated automatically. (in target
'App' from project 'App')

These are warnings we could probably ignore, but I'm not sure we want to run this with --allow-warnings. WDYT?

@jtreanor
Copy link
Copy Markdown
Contributor Author

jtreanor commented Oct 3, 2019

The cause of the warning was actually:

WARN  | source: Git sources should specify a tag.

That was because I was running it on a branch instead of a tag for testing purposes. I have made a new, working test build here. It also posted successfully to Slack:

image

I think we should avoid --allow-warnings if at all possible.

Copy link
Copy Markdown
Contributor

@jkmassel jkmassel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice – it's passing now, and I see the notification in Slack.

Looks good!

:shipit:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants