Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-7887 Release automation improvement
  3. BEAM-6598

build_release_candidate.sh fails because of leftover RC tags in working git clone

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • P3
    • Resolution: Unresolved
    • None
    • None
    • build-system
    • None

    Description

      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)

      Attachments

        Issue Links

          is a clone of

          Sub-task - The sub-task of the issue BEAM-6595 build_release_candidate.sh should not push to apache org on github

          • P3 - Non-urgent bugs, features, and improvements
          • Resolved
          is cloned by

          Sub-task - The sub-task of the issue BEAM-6613 build_release_candidate.sh fails if RC > 1 but there's no SVN directory on dist.apache.org

          • P3 - Non-urgent bugs, features, and improvements
          • Open

          Activity

            People

              Unassigned Unassigned
              kenn Kenneth Knowles
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: