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

Prevent Elastic Agents capabilities from becoming available when AWS configuration is unset

XMLWordPrintable

      Issue

      Elastic Agents and its capabilities are available in Bamboo, even though AWS is not configured.

      How to replicate

      • Install Bamboo v6.x
      • Create a Plan
      • Go to Plan configuration >> [Stage] >> [Job] >> Requirements tab
      • Search for JDK and you will notice JDK 8, JDK 1.9, JDK 10 will become available even though you have not set them up as capabilities in Bamboo administration >> Overview >> Build resources >> Server capabilities
      • Go to Bamboo administration >> Overview >> Build resources >> JDKs and you will not find them listed
      • Enable AWS configuration in Bamboo
      • Go to Bamboo administration >> Overview >> Build resources >> JDKs and you will find them listed

      Notes

      The same issue can be seen when setting up tasks that require capabilities, e.g Maven 3.x. The Build JDK dropdown menu displays Elastic Agents capabilities when AWS is not configured.

            [BAM-20122] Prevent Elastic Agents capabilities from becoming available when AWS configuration is unset

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 23 June 2020

            Hi,

            Thank you for raising this issue. 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. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

            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 - 23 June 2020 Hi, Thank you for raising this issue. 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. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. 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

              Unassigned Unassigned
              rsperafico Rafael Sperafico (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: