https://github.com/ml-opensource/bitrise-certificate-validation-step

Custom Bitrise step to validate the expiration dates of code signing certificates uploaded to Bitrise
https://github.com/ml-opensource/bitrise-certificate-validation-step

Last synced: 8 days ago
JSON representation

Custom Bitrise step to validate the expiration dates of code signing certificates uploaded to Bitrise

• Host: GitHub
• URL: https://github.com/ml-opensource/bitrise-certificate-validation-step
• Owner: ml-opensource
• License: mit
• Created: 2023-02-16T14:54:20.000Z (almost 2 years ago)
• Default Branch: main
• Last Pushed: 2023-02-22T08:42:44.000Z (over 1 year ago)
• Last Synced: 2024-11-10T22:18:30.901Z (8 days ago)
• Language: Go
• Size: 30.3 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Code signing certificate - expiration check

This Bitrise step checks that at least one certificate is uploaded for the app in Bitrise and that all the uploaded certificates have valid expiration dates.

This step is designed to be used with [Apple Cloud Signing](https://github.com/nodes-ios/Playbook/blob/master/ci/bitrise-complete-guide-cloud-signing.md) which requires a development code signing certificate to be uploaded. 

## The problem this step solves

If the certificate uploaded to Bitrise expires, Cloud Signing ignores it and starts creating new development certificates on Apple portal. However, this creates

a new development certificate for every new build (the private key does not get transfered to a new fresh cloud machine) and soon we hit the limit for number of allowed certificates on Apple portal. This step prevents that by failing the build 

when the uploaded development certificate expires.