[
https://issues.apache.org/jira/browse/BEAM-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174769#comment-17174769
]
Beam JIRA Bot commented on BEAM-6599:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> build_release_candidate.sh should not be interactive
> ----------------------------------------------------
>
> Key: BEAM-6599
> URL: https://issues.apache.org/jira/browse/BEAM-6599
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Kenneth Knowles
> Priority: P2
> Labels: stale-P2
>
> The build_release_candidate.sh script takes a long time to run. That means it
> is going to be in another tab or a person will (or anyhow SHOULD) walk away
> while it runs. It is very inefficient that it has interactive prompts that
> stop it completing.
> It asks a few interactive questions at the beginning. This is OK but they
> could even more easily be command line flags.
> Later there's y/n questions and can even be gpg interactions while it is
> running. They should all be noninteractive. The gpg key can be unlocked
> before launch by signing a dummy file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
