-
Notifications
You must be signed in to change notification settings - Fork 488
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
Windows build fails to sign the application #4243
Comments
As part of this change we want to migrate the certificate handling over to vault (cf. https://github.com/bpmn-io/internal-docs/issues/802). |
Reached out to internally (IT) for further investigation. |
Shared updated certificate with @marstamm; you should now be unblocked to work on this issue. |
Cross-posting my assessment (yesterday) here:
|
Summary update from internal Slack:
|
This ensures we can build windows releases until a solution for #4243 is integrated.
This ensures we can build windows releases until a solution for #4243 is integrated.
[Update] We disabled Code signing on Windows for now. @philippfromme has the physical token for backup signing. DigiCert purchase is still in progress |
I just asked @KerstinHebel for update on https://helpdesk.camunda.com/support/tickets/14320. What is the status of "DigiCert purchase"? I know that we are forced right now to use a hardware key, but I believe it's unhealthy to require from @philippfromme signing the executable. |
What should we do?
Update our Certificates we use to sign the application during the build process. The windows certs expired on Apr 11.
cf. https://github.com/camunda/camunda-modeler/actions/runs/8681071392
Why should we do it?
To ensure we can release the camunda modeler on windows
The text was updated successfully, but these errors were encountered: