-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add Azure code signing for the Windows release DLLs #108
Conversation
76bcc7d
to
c7f84c6
Compare
c7f84c6
to
68f4f14
Compare
This can be merged independent of this CI, because the PR has no access the the GitHub secret. |
endpoint: https://weu.codesigning.azure.net/ | ||
code-signing-account-name: mixxx | ||
certificate-profile-name: mixxx | ||
files-folder: ${{ matrix.vcpkg_path }}/installed/${{ matrix.vcpkg_triplet }}/bin |
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.
files-folder: ${{ matrix.vcpkg_path }}/installed/${{ matrix.vcpkg_triplet }}/bin | |
files-folder: ${{ matrix.vcpkg_path }}/installed/${{ matrix.vcpkg_triplet }}/ | |
files-folder-recurse: true |
Otherwise, the Qt plugin DLLs remain unsigned
I don't think we need to sign .exe files, because we don't ship .exe binaries from VCPKG. But we need to sign the .dll files from the plugins directory as suggested above. |
c9537d3
to
afc98d3
Compare
Oh, I have missed to adjust the root folder for signing. The exe files, I have added, because we can this way allow the contributors to verify the build tools as well. |
afc98d3
to
b7f4c0f
Compare
Signing all recursive fails with
Now trying to select the plugins folder explicit. |
Can you report it upstream - AFAIK Azure Code Signing is still in Beta and they need our feedback |
LGTM! Thank you! |
No description provided.