-
Bug
-
Resolution: Fixed
-
Low
-
5.9.1, 5.9.3
-
None
This issue was reported at BAM-13631 and was supposedly fixed in 5.6.0.
Just tested this in Bamboo 5.9.3 and issue still exist.
Steps to replicate
- Create an agent with NodeJS capability
- Create an agent without NodeJS capability
- Add the NodeJS task in a deployment environment task
- Observe the number of agents capable of running the deployment
The agent without the NodeJS still shows as a capable agent.
[BAM-16229] Agents not capable of running deployment tasks still show as available agents
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1435293 ] | New: JAC Bug Workflow v3 [ 3382271 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1409886 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1435293 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 933282 ] | New: Bamboo Workflow 2016 v1 [ 1409886 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Fix Version/s | New: 5.10.0 [ 54320 ] |
Remote Link | New: This issue links to "BDEV-9929 (Atlassian JIRA Extranet - Special Projects)" [ 114712 ] |
Component/s | New: Deployments [ 19692 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Open [ 1 ] |