...
This problem is caused by an upstream bug introduced in Bamboo 5.9.1 and addressed in Bamboo 5.12.0.2:
| Jira Legacy |
|---|
| server | Atlassian JIRA |
|---|
| serverId | 144880e9-a353-312f-9412-ed028e8166fa |
|---|
| key | BAM-17488 |
|---|
|
Accordingly, you can address it by either upgrading Bamboo to a release that contains a respective fix, or by updating to Tasks for AWS 2.10.4, which provides a respective workaround (refer to | Jira Legacy |
|---|
server | JIRA (https://utoolity.atlassian.net)| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | fac61c2e-db0a-39da-bb3c-e0dc0ef556f0 |
|---|
key | /browse/UAA-168 for details).
...
|
|---|
Feature flagThe workaround avoids the build log flooding by skipping the creation of variables if they are password variables (variable name contains "password", "awsSecretKey" or "passphrase") and the variable value contains only asterisks. For the (unlikely) case that this would affect any existing build configurations, the workaround can be disabled by setting a global or plan variable utoolity.flags.disableWorkaroundForBAM17488 to true. |
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | UAAKB |
|---|
| sort | modified |
|---|
| showSpace | false |
|---|
|
...
| | reverse | true |
|---|
| type | page |
|---|
| cql | label in ( "tasks-for-aws" , "memory" , "exception" , "heap" ) and type = "page" and space = "UAAKB" |
|---|
| labels | tasks-for-aws exception memory heap |
|---|
|