[
https://issues.apache.org/jira/browse/BEAM-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754123#comment-16754123
]
Kenneth Knowles edited comment on BEAM-6192 at 1/28/19 4:33 PM:
----------------------------------------------------------------
- I ran it on my desktop but then walked away, didn't realize it had a bunch
of interactive prompts. I would suggest simply removing those so it can run to
completion without babysitting.
- Failed when staging Python binaries, then I'm not sure how to restart where
it left off or rebuild from the same commit without extra tagging commits, etc.
- The failure was an issue with global Python libraries; I basically have none
because I only use virtualenv
was (Author: kenn):
- I ran it on my desktop but then walked away, didn't realize it had a bunch
of interactive prompts. I would suggest simply removing those so it can run to
completion without babysitting.
- Failed when staging Python binaries, then I'm not sure how to restart where
it left off or rebuild from the same commit without extra tagging commits, etc.
> 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 Jayalath
> Assignee: Boyuan Zhang
> Priority: Major
>
> 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
(v7.6.3#76005)
