[
https://issues.apache.org/jira/browse/BEAM-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122936#comment-17122936
]
Beam JIRA Bot commented on BEAM-6598:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
