[
https://issues.apache.org/jira/browse/BEAM-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752876#comment-16752876
]
Kenneth Knowles edited comment on BEAM-6192 at 1/26/19 1:01 AM:
----------------------------------------------------------------
I am going to make some notes of things during 2.10.0:
Verify:
- Of all the things the verify script checked on, it didn't check docker so
that's where I failed
- I hit some flakes, of course. Or anyhow I think they were flakes...
- I don't think --no-parallel is needed any more
Build RC
- Could use {{mktemp}} to use a temp dir instead of something in home dir
- I would like to be able to re-run the script without having to sit and
interactively re-type vars. Maybe that is just a matter of instructions.
- Should not tag the commit until last; I think this is the gradle release
plugin's fault. I had to delete a tag from GitHub
- Had to replace https://github.com/apache/beam in the script with
[email protected]:apache/beam
- Also I think this can be parallel now
I imagine shell scripts are an OK entry point for using Jenkins to produce
candidates for us. It does seem like the gradle release plugin is not worth the
trouble. It mimics the maven release plugin but I'm not really sure what that
is needed for.
was (Author: kenn):
I am going to make some notes of things during 2.10.0:
Verify:
- Of all the things the verify script checked on, it didn't check docker so
that's where I failed
- I don't think --no-parallel is needed any more
Build RC
- Could use {{mktemp}} to use a temp dir instead of something in home dir
- I would like to be able to re-run the script without having to sit and
interactively re-type vars. Maybe that is just a matter of instructions.
- Should not tag the commit until last; I think this is the gradle release
plugin's fault. I had to delete a tag from GitHub
- Had to replace https://github.com/apache/beam in the script with
[email protected]:apache/beam
- Also I think this can be parallel now
I imagine shell scripts are an OK entry point for using Jenkins to produce
candidates for us. It does seem like the gradle release plugin is not worth the
trouble. It mimics the maven release plugin but I'm not really sure what that
is needed for.
> 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)
