-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat(windows-sign): add unstable ssl.com windows signing #425
Conversation
main outstanding question is names of the SECRETS which I made up and don't match ssl.com's defaults. They use ES_USERNAME, ES_PASSWORD, CREDENTIAL_ID, and ES_TOTP_SECRET ("es" is "esign"). |
{{%- if global_task %}} | ||
- upload-global-artifacts | ||
{{%- endif %}} | ||
runs-on: "ubuntu-20.04" |
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.
Nice we can run it on not-Windows.
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.
yeah it's pure java, running it on windows is actually harder (they ship the whole jvm x3)
uses: sslcom/esigner-codesign@develop | ||
with: | ||
command: batch_sign | ||
username: ${{ secrets.SSL_CODESIGN_USER }} |
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 think using an SSLCOM
prefix would make this a little clearer to me.
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 changed everything to SSLDOTCOM/ssldotcom prefixes (matches how we treat axo.dev) and made these match a bit more with the action's defaults.
73fcbff
to
6af290a
Compare
ssldotcom-windows-sign=true
No description provided.