-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tweak code signing lanes naming and make them all public #23991
Conversation
This way, we can better code complete
Full name `update_certs_and_profiles_wordpress_enterprise`
Full name `update_certs_and_profiles_wordpress_app_store`
Full name `update_certs_and_profiles_jetpack_enterprise`
Full name `update_certs_and_profiles_jetpack_app_store`
This way, we can call them when it's time to regenerate the profiles for one single combination without hacking the `Fastfile`.
This will avoid API redirects
📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
fastlane/lanes/codesign.rb
Outdated
@@ -126,6 +142,7 @@ def update_code_signing(type:, team_id:, readonly:, app_identifiers:, api_key_pa | |||
match( | |||
storage_mode: 's3', | |||
s3_bucket: 'a8c-fastlane-match', | |||
s3_region: 'us-east-2', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we could use here the same storage options constant you added on Woo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Addressed in b10ce3e
Maybe we could also push that constant in release-toolkit
, to guarantee it's the same across projects. And the same could be done for sets of env vars that we check here and there.
@@ -126,6 +142,7 @@ def update_code_signing(type:, team_id:, readonly:, app_identifiers:, api_key_pa | |||
match( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also after seeing https://github.com/woocommerce/woocommerce-ios/pull/14911/files#diff-dff4b99d4e651ab9d7597876ec8dbe92aa934e42c0fb55f4aadd6c106fc96688R1153, I wonder if we should try and use a consistent name (match
/ sync_code_signing
) across projects 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great point @iangmaia !
I clearly missed that this was called via match
, otherwise I would have updated it to sync_code_signing
like I've done elsewhere. But since you raised the question, I thought I'd bubble it up internally to have an official discussion about team's preferences: paaHJt-7Je-p2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I clicked the "Merge when ready" without addressing this suggestion. I just want to wait and see what the outcome of the discussion is. Given I linked to here in the discussion, I'll be able to followup what that has taken place.
Next step... move the constant to release toolkit?
This was done in the context of regenerating soon expiring certificates, see pdnsEh-1ZG-p2
I tweaked the name to be hierarchical. That is, the lane that updates everything is
update_certs_and_profiles
, the lane that updates all the WordPress variants isupdate_certs_and_profiles_wordpress
, the lane that update only the WordPress App Store variant isupdate_certs_and_profiles_wordpress_app_store
.I also made all lanes public, so they can be called individually, and added new lanes for updating both app's App Store or Enterprise code siging.
Testing
I run these locally as part of the certificates update work.
Regression Notes
PR submission checklist:
RELEASE-NOTES.txt
if necessary. N.A.UI changes testing checklist: Not a UI PR.