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

present a message to remote client if /api/rest/updateAndBuild.action?buildKey=PLAN-KEY did not trigger a build

    • Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • None
    • REST API
    • None
    • 0
    • 1
    • 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.

      currently the remote client is presented with

       A build of xyz project - PlanName was triggered by remote http call.

      even when no build has been triggered due to no changes.
      If no build is triggered due to no changes are present - then a different message should be displayed like

       No changes found for project xyz - PlanName : no build triggered on bamboo host 

            [BAM-3238] present a message to remote client if /api/rest/updateAndBuild.action?buildKey=PLAN-KEY did not trigger a build

            Please remember, that this API is deprecated.
            Currently, you can use new REST API to trigger the build:

            /rest/api/latest/queue

            as described here: http://docs.atlassian.com/bamboo/REST/3.3-SNAPSHOT/#idp161696

            To trigger the build you need to execute POST request specifying project and plan key.
            There is a number of HTTP error codes returned, when build is not triggered.

            Documentation is for version 3.3, but it applies also for previous versions (2.7+).

            Marek Went (Inactive) added a comment - Please remember, that this API is deprecated. Currently, you can use new REST API to trigger the build: /rest/api/latest/queue as described here: http://docs.atlassian.com/bamboo/REST/3.3-SNAPSHOT/#idp161696 To trigger the build you need to execute POST request specifying project and plan key. There is a number of HTTP error codes returned, when build is not triggered. Documentation is for version 3.3, but it applies also for previous versions (2.7+).

            Even if this API call would be reserved for repository scripts it would still be nice to get a different message.
            Would make things much easier if you are testing your new script and are wondering why the plan does not run.

            Dennis Benzinger | SAP added a comment - Even if this API call would be reserved for repository scripts it would still be nice to get a different message. Would make things much easier if you are testing your new script and are wondering why the plan does not run.

            https://support.atlassian.com/browse/BSP-1361

            this may not be necessary if we reserve this api call for repository scripts only - that is you HAVE to specify an IP address (of the repo server)

            Ulrich Kuhnhardt [Atlassian] added a comment - https://support.atlassian.com/browse/BSP-1361 this may not be necessary if we reserve this api call for repository scripts only - that is you HAVE to specify an IP address (of the repo server)

              Unassigned Unassigned
              ukuhnhardt Ulrich Kuhnhardt [Atlassian]
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: