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

Expose "Custom Build Flag" on /result API GET requests

XMLWordPrintable

    • 0

    • 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.

      Problem Definition

      When viewing results of an API call for build results, there is not a way to distinguish results which were 'run customized'

      Suggested Solution

      We already flag custom runs in the UI with the "Custom Build" flag. Can we expose this flag on the API?

      Workaround

      add a script task within the Bamboo plan, that will add a 'Label' to the build results if a certain global variable = TRUE. Then when running the customized build, override the global variable to be equal to true. This will add the label to the build results, which is visable in the API.

      http://myhost.com:8085/rest/api/latest/result/{projectKey}-{buildKey}-{buildNumber}/label

            [BAM-20011] Expose "Custom Build Flag" on /result API GET requests

            Martyna Wojtas (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 7 April 2020

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

             

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 7 April 2020 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.   Thank you, Bamboo Team
            Martyna Wojtas (Inactive) made changes -
            Labels New: bamboo-bugs-grooming
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3015056 ] New: JAC Suggestion Workflow 3 [ 3601431 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2749384 ] New: JAC Suggestion Workflow [ 3015056 ]
            Alexey Chystoprudov made changes -
            Component/s New: REST API [ 11601 ]
            Krystian Brazulewicz made changes -
            UIS New: 0
            Robert W (Inactive) made changes -
            Affects Version/s New: 6.6.1 [ 80799 ]
            Robert W (Inactive) made changes -
            Description Original: h3. Problem Definition

            When viewing results of an API call for build results, there is not a way to distinguish results which were 'run customized'

            h3. Suggested Solution

            We already flag custom runs in the UI with the "Custom Build" flag. Can we expose this flag on the API?
             
            h3. Workaround

            add a script task within the Bamboo plan, that will add a 'Label' to the build results if a certain global variable = TRUE. Then when running the customized build, override the global variable to be equal to true. This will add the label to the build results, which is visable in the API.

            {{http://myhost.com:8085/rest/api/latest/result/{projectKey}-{buildKey}-{buildNumber}/label}}

            		New: h3. Problem Definition

            When viewing results of an API call for build results, there is not a way to distinguish results which were 'run customized'

            h3. Suggested Solution

            We already flag custom runs in the UI with the "Custom Build" flag. Can we expose this flag on the API?
             
            h3. Workaround

            add a script task within the Bamboo plan, that will add a 'Label' to the build results if a certain global variable = TRUE. Then when running the customized build, override the global variable to be equal to true. This will add the label to the build results, which is visable in the API.

            {noformat}
            http://myhost.com:8085/rest/api/latest/result/{projectKey}-{buildKey}-{buildNumber}/label
            {noformat}

            Robert W (Inactive) created issue -

              Unassigned Unassigned
              rwatson@atlassian.com Robert W (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: