-
Bug
-
Resolution: Fixed
-
Medium
-
None
When assigning agents to an environment, agents that are not able to complete all the tasks required are still listed. Our documentation states that "Only agents applicable to the deployment environment will be available for selection," which is not true.
In my test instance, I removed the Ant Capability^agent.png
from one of my Remote Agents, and [added a task for Ant to my environment^antneeded.png]. However, the agent it is still listed as a "capable server" when looking at either the tasks view^tasksview.png
for my deployment environment, or when setting a dedicated agent^dedicated.png
for the environment.
This is problematic because Bamboo will chose a capable agent if you do not set a dedicated agent. This is from the "Edit agents" page:
If you do not assign an agent to this deployment, one will be chosen at run time according to standard requirement/capability mappings.
If an agent cannot perform all of the tasks because it lacks a capability, it should not be listed. Moreover, Bamboo will still attempt to use this server, and if it does, the deployment will fail needlessly.
[BAM-13631] Agents not capable of running deployment tasks still show as available agents
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1437243 ] | New: JAC Bug Workflow v3 [ 3380441 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1422051 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1437243 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 606411 ] | New: Bamboo Workflow 2016 v1 [ 1422051 ] |
| Remote Link | New: This issue links to "BDEV-9929 (Atlassian JIRA Extranet - Special Projects)" [ 114711 ] |
@Jeremy Frederick
This has been fixed using plugin: 'Requirement for Deployments' https://marketplace.atlassian.com/plugins/com.atlassian.bamboo.plugin.requirementtask
| Remote Link | Original: This issue links to "Page (Extranet)" [ 85810 ] | New: This issue links to "Page (Extranet)" [ 85810 ] |
| Remote Link | Original: This issue links to "Page (Extranet)" [ 85810 ] | New: This issue links to "Page (Extranet)" [ 85810 ] |
| Remote Link | Original: This issue links to "Page (Extranet)" [ 85810 ] | New: This issue links to "Page (Extranet)" [ 85810 ] |
rajinel.prasad@optiver.com.au Unfortunately this fix does not work for Cloud instances. Any other suggestions in this case?