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

Option to set a trigger IP address globally and for all repository types

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Triggers
    • None
    • 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.

    Description

      When migrating plan repositories e.g. to Bitbucket Cloud (or any other no Bitbucket Server repository), for the "Remote trigger" type, a WebHook and a "Trigger IP address" has to be specified.

      For not needing to update that IP address manually and plan per plan, a global Bamboo setting would be great allowing to whitelist that IP address used for "Remote trigger".

      This could, for example, be just another tab under Cog >> Overview >> Repository settings.

      What is currently possible is to utilize Bamboo's bulk actions, like so:

      • As Bamboo Admin user navigate to Cog >> Overview >> Bulk action and there select "Replace triggers" and press button "Next".
      • Select the plans wished underneath your projects of choice and press button "Next" again.
      • That brings you to a page where you can select "Trigger type". Choose "Remote trigger" there and find opening field "Trigger IP addresses" where you can perform the change.

      Another great alternative to providing a place for global Bamboo setting for changing that IP trigger address might be prividing an appropriate REST API endpoint. Or even both.

      Attachments

        Activity

          People

            Unassigned Unassigned
            gforster@atlassian.com Gerhard Forster (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: