Skip to content
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

Merged
merged 10 commits into from
Jan 21, 2025

Conversation

mokagio
Copy link
Contributor

@mokagio mokagio commented Jan 20, 2025

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 is update_certs_and_profiles_wordpress, the lane that update only the WordPress App Store variant is update_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

  1. Potential unintended areas of impact – N.A.
  2. What I did to test those areas of impact (or what existing automated tests I relied on) – N.A.
  3. What automated tests I added (or what prevented me from doing so) – N.A.

PR submission checklist:

  • I have completed the Regression Notes.
  • I have considered adding unit tests for my changes. N.A.
  • I have considered adding accessibility improvements for my changes. N.A.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary. N.A.

UI changes testing checklist: Not a UI PR.

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`.
@mokagio mokagio requested a review from a team January 20, 2025 04:24
@mokagio mokagio self-assigned this Jan 20, 2025
@mokagio mokagio added the Tooling Build, Release, and Validation Tools label Jan 20, 2025
@mokagio mokagio added this to the Pending milestone Jan 20, 2025
@mokagio mokagio marked this pull request as ready for review January 20, 2025 04:25
@wpmobilebot
Copy link
Contributor

wpmobilebot commented Jan 20, 2025

WordPress Alpha📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.
App NameWordPress Alpha WordPress Alpha
ConfigurationRelease-Alpha
Build Numberpr23991-b10ce3e
Version25.6
Bundle IDorg.wordpress.alpha
Commitb10ce3e
App Center BuildWPiOS - One-Offs #11374
Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Jan 20, 2025

Jetpack Alpha📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.
App NameJetpack Alpha Jetpack Alpha
ConfigurationRelease-Alpha
Build Numberpr23991-b10ce3e
Version25.6
Bundle IDcom.jetpack.alpha
Commitb10ce3e
App Center Buildjetpack-installable-builds #10407
Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

Copy link
Contributor

@iangmaia iangmaia left a comment

Choose a reason for hiding this comment

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

👍

@@ -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',
Copy link
Contributor

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.

Copy link
Contributor Author

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(
Copy link
Contributor

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 🤔

Copy link
Contributor Author

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

Copy link
Contributor Author

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?
@mokagio mokagio enabled auto-merge January 21, 2025 18:55
@mokagio mokagio added this pull request to the merge queue Jan 21, 2025
Merged via the queue into trunk with commit 4546518 Jan 21, 2025
25 checks passed
@mokagio mokagio deleted the mokagio/public_match_lanes branch January 21, 2025 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tooling Build, Release, and Validation Tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants