Page MenuHomePhabricator

[CI] Get rid of KEYCHAIN_PASSWORD GitHub secret
ClosedPublic

Authored by ashoat on Oct 25 2023, 11:37 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 24, 5:52 PM
Unknown Object (File)
Thu, Nov 21, 9:32 AM
Unknown Object (File)
Wed, Nov 20, 4:52 AM
Unknown Object (File)
Oct 28 2024, 8:18 PM
Unknown Object (File)
Oct 5 2024, 1:09 AM
Unknown Object (File)
Oct 4 2024, 2:00 AM
Unknown Object (File)
Oct 4 2024, 2:00 AM
Unknown Object (File)
Oct 4 2024, 2:00 AM
Subscribers

Details

Summary

Based on this doc, this value doesn't matter. We have it set to a random string via GitHub secrets, but we might as well just use some hardcoded string.

The benefit here is simplifying the set of secrets we need somebody to configure to get a fork of the Comm repo working with our CI workflows (so they can be debugged).

Test Plan

CI will test after landing

Diff Detail

Repository
rCOMM Comm
Branch
ashoat/ci
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Upon further research, it looks like this is only relevant for runners that are reused for multiple runs of workflows OR for machines that are being used for unrelated workflows that shouldn't have access to these certificates.

Because these macOS runners are ephemeral, providing a KEYCHAIN_PASSWORD isn't necessary. The "Clean up keychain" step is also unnecessary and could be removed.

This revision is now accepted and ready to land.Oct 25 2023, 2:58 PM

Remove "Clean up keychain" step

This revision was landed with ongoing or failed builds.Oct 25 2023, 3:03 PM
This revision was automatically updated to reflect the committed changes.