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

Add the ability to automatically tag the source repository

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.2
    • Builds
    • 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.

      People want the ability to be able to automatically tag a build after it completes successfully. e.g tagging a build as LATEST_SUCCESSFUL when it completes successfully.

      That way, other tools / users can always point the tag for the latest successful builds

            [BAM-620] Add the ability to automatically tag the source repository

            MarkC added a comment -

            This functionality is now available as a Task in 3.2 for Subversion.

            Other repository types will be supported in the future

            MarkC added a comment - This functionality is now available as a Task in 3.2 for Subversion. Other repository types will be supported in the future

            edwin added a comment -

            Hi guys,

            This functionality is available through the Bamboo Tagger plugin.

            Much appreciation goes to Ross and Jonathan for their efforts on this plugin.

            For future issues about this plugin, please use the Bamboo Tagger plugin project

            Cheers,
            Edwin

            edwin added a comment - Hi guys, This functionality is available through the Bamboo Tagger plugin . Much appreciation goes to Ross and Jonathan for their efforts on this plugin. For future issues about this plugin, please use the Bamboo Tagger plugin project Cheers, Edwin

            +1 on the original description, not on Arash M's comment.

            We need a tag that we can always point to "tags/latest" that is always the most up-to-date successfully-built codebase.

            David A. Riggs added a comment - +1 on the original description, not on Arash M's comment. We need a tag that we can always point to "tags/latest" that is always the most up-to-date successfully-built codebase.

            Arash M added a comment -

            The labeling of the repository should be allowed at 2 different places in the work flow :

            1) When the build is triggered (automatically or manually) there should be an option to label the repository to represent all the versions of the files represented in the build.

            2) When there is a successful, a label could be throw on the repository to represent all the versions of the files represented in the successful build. Or maybe, the label that was thrown on at the beginning of the build could be modified to show that the build was a successful build.

            This can be performed by our build scripts, but since the syncing of the code for build purposes is done by Bamboo, it makes sense that Bamboo also label the repository, or atleast provide the option.

            Thanks,
            Arash

            Arash M added a comment - The labeling of the repository should be allowed at 2 different places in the work flow : 1) When the build is triggered (automatically or manually) there should be an option to label the repository to represent all the versions of the files represented in the build. 2) When there is a successful, a label could be throw on the repository to represent all the versions of the files represented in the successful build. Or maybe, the label that was thrown on at the beginning of the build could be modified to show that the build was a successful build. This can be performed by our build scripts, but since the syncing of the code for build purposes is done by Bamboo, it makes sense that Bamboo also label the repository, or atleast provide the option. Thanks, Arash

              Unassigned Unassigned
              mark@atlassian.com MarkC
              Votes:
              21 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: