[
https://issues.apache.org/jira/browse/FLINK-25301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-25301:
-------------------------------------
Description:
Signing binaries is currently done as part of the creation of binaries.
However, this signing is optional, which is useful if you're building the
release on another machine.
To do that you need to dig into the scripts to figure out what actually needs
to be signed and which property you need to set to skip the signing when
creating the binaries.
Instead we should decouple these steps, with 1 script creating all binaries and
1 script doing the signing.
was:
Signing binaries is currently done as part of the creation of binaries.
However, this signing is optional, which is useful if you're building the
release on another machine.
However, when you do that you now have to dig into the scripts to figure out
what actually needs to be signed and which property you need to set to skip the
signing when creating the binaries.
Instead we should decouple these steps, with 1 script creating all binaries and
1 script doing the signing.
> Add a separate script for signing binaries
> ------------------------------------------
>
> Key: FLINK-25301
> URL: https://issues.apache.org/jira/browse/FLINK-25301
> Project: Flink
> Issue Type: Sub-task
> Components: Release System
> Reporter: Chesnay Schepler
> Priority: Major
>
> Signing binaries is currently done as part of the creation of binaries.
> However, this signing is optional, which is useful if you're building the
> release on another machine.
> To do that you need to dig into the scripts to figure out what actually needs
> to be signed and which property you need to set to skip the signing when
> creating the binaries.
> Instead we should decouple these steps, with 1 script creating all binaries
> and 1 script doing the signing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
