I was always under the impression that artifact creation, signing and staging for voting we always wanted to be "automated" in some way. I believe we could have a jenkins job do this if we had a good way to transfer the release managers signing keys to a Jenkins worker (via cloud key management system?). So should we we should focus on better and more reliable release automation instead of making the release scripts more interactive?
On Fri, Jan 10, 2020 at 9:37 AM Udi Meiri <[email protected]> wrote: > What does the community think about converting our release scripts > <https://github.com/apache/beam/tree/master/release/src/main/scripts> to > be Jupyter notebooks using bash_kernel? > > Since these scripts frequently fail (especially for first time releasers), > we often need to rerun parts manually. The notebook format lets you do that. > > Certain steps require verification/inspection, such as before pushing > commits. This is naturally done by spitting into multiple notebook cells. > > The notebook format also lends itself well to inline documentation and > on-the-fly modification. > > >
