[
https://issues.apache.org/jira/browse/BEAM-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17548104#comment-17548104
]
Danny McCormick commented on BEAM-6598:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/19758
> 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: Sub-task
> Components: build-system
> Reporter: Kenneth Knowles
> Priority: P3
>
> 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.20.7#820007)
