Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-9226

Ability to change VCS Revision number after a build is finished

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Customer use case;

      While using Bamboo with the BRMP plugin to trigger "release builds".
      During the release builds, we would like the build script to automatically update the "version" of our Maven POMs (using the Versions Maven plugin), and commit these changes to our Git repository, so that the release build is reproducible.
      I have implemented all this in our build plan, but the problem is that Bamboo captures the commit ID at the start of the build, and does not update its records with the new post-commit commit ID. This has two consequences:

      • the commit ID recorded with the build does not match the actual code used for the build
      • Bamboo then triggers another build because it detects a commit after the one that triggered the build.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              asridhar AjayA
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: