-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-48904: [C++][FlightRPC][CI][Packaging] Upload ODBC installer into GitHub release as RC #48934
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
Changes from all commits
65b9bd4
defaba1
7f2d797
6bb67c5
74549fe
51acfe6
b1cf045
2fb7436
7bd8429
195ed13
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We need to add signing command line something like the following here: diff --git a/dev/release/05-binary-upload.sh b/dev/release/05-binary-upload.sh
index f628cce0e0..e66b5af646 100755
--- a/dev/release/05-binary-upload.sh
+++ b/dev/release/05-binary-upload.sh
@@ -98,6 +98,9 @@ upload_to_github_release() {
shasum -a 512 "${base_name}" >"${base_name}.sha512"
popd
fi
+ if [[ "${base_name}" = *.msi ]]; then
+ jsign ... "${dist_dir}/${base_name}"
+ fi
done
gh release upload \
--repo apache/arrow \
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the suggestion @kou. My understanding is that this change will be done by a PMC member outside of this PR. Please correct me if that’s not the case
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It appears there's documentation here: https://github.com/apache/infrastructure-website/blob/145ccc3f7dadf0b95418ebb31c86c349b482fb01/content/pages/code-signing-use.md?plain=1 That provides the Do we need to sign the DLL inside the MSI as well or just sign the MSI?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hey @kou, I looked at this the other week and found this page from ASF: https://infra.apache.org/code-signing-use.html. There's an automated signing option that I haven't tested but it looks like we might be able to obtain a secret, the "local file" they refer to here:
and then we could do this in CI. Otherwise it would be done manually which isn't ideal. Have you done this before? Edit: I re-read the page and the jsign method in Step 4 looks very doable in CI so long as a PMC member applies for an account to set up the secret.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seems it is considered best practice to sign the DLL inside MSI: https://stackoverflow.com/a/4716079
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hey @alinaliBQ, a PMC member can take the next steps. @kou @lidavidm: Signing in CI is acceptable (per Slack) and it sounds like having a reproducible build for the installer is key. I assume the work done on setting up reproducible builds at the project level can be extended to the ODBC installer. Do we just need a volunteer at this point to figure the rest of this out?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK. Let's work on reproducible build as a separated task.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note that we can't release the ODBC installer without signing. If we can't prepare reproducible build until the next release, we may need to prepare manual signing script like the diff in the #48934 (comment) comment.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you revert needless permission change?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup, I reverted it. it was changed accidentally |
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.
Could you revert needless permission change?
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.
Yup, I reverted it. it was changed accidentally