[
https://issues.apache.org/jira/browse/BEAM-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122189#comment-17122189
]
Kenneth Knowles commented on BEAM-6192:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Release related scripts should be more resilient to failures
> ------------------------------------------------------------
>
> Key: BEAM-6192
> URL: https://issues.apache.org/jira/browse/BEAM-6192
> Project: Beam
> Issue Type: Improvement
> Components: project-management, testing
> Reporter: Chamikara Madhusanka Jayalath
> Assignee: Kenneth Knowles
> Priority: P2
> Labels: stale-assigned
>
> Currently we have a number of great release related scripts that are
> mentioned in Beam release guide.
> [https://beam.apache.org/contribute/release-guide/]
>
> These tools are great but I think given the length of these scripts, we
> should make them more resilient to error conditions and make them retry
> commands (after user action) as much as possible.
> For example, RC creation script might fail for a number of reasons (it failed
> for me due to tox not being available for example) and halt at an
> intermediate state (some files staged, some commits done to Github but not
> complete). Re-running script fails due to previous state. After this it is up
> to the release manager to figure out where the script failed, do cleanups,
> and resume the process.
>
> Also, have we considered using some release automation tooling instead of
> shell scripts ?
>
> [~boyuanz] assigning this to you since you developed some of these. Please
> feel free to re-direct.
>
> cc: [~altay]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
