You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/04/20 22:03:03 UTC

[jira] [Assigned] (BEAM-6598) build_release_candidate.sh fails because of leftover RC tags in working git clone

     [ https://issues.apache.org/jira/browse/BEAM-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles reassigned BEAM-6598:
-------------------------------------

    Assignee:     (was: Kenneth Knowles)

> build_release_candidate.sh fails because of leftover RC tags in working git clone
> ---------------------------------------------------------------------------------
>
>                 Key: BEAM-6598
>                 URL: https://issues.apache.org/jira/browse/BEAM-6598
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Kenneth Knowles
>            Priority: Major
>
> Currently, the build_release_candidate.sh re-uses $HOME/build_release_candidate/beam as the git clone. If the RC tag already exists due to a prior build, it crashes. Instead, since that clone failed, it should just not be used the next time. The workflow that makes sense to me is:
>  - Locally tag the intended RC<n> commit
>  - Try to build the RC from that
>  - If the RC build fails, remove tag / discard working branch / etc
>  - If the RC succeeds, push the tag (and if it is on a gradle release plugin commit, those commits)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)