-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
3
-
2
-
Issue Summary
Currently, Bamboo is only looking for a successful response code with a PowerShell script. So, by default, if you run a PowerShell script task with some non existing command, Bamboo will mark this task as successful.
Steps to Reproduce
- Create a script task with powershell interpreter and coma content like "idonotexist"
- Run the plan
Expected Results
Script task fails
Actual Results
Script task is green even though the above command will cause an error.
Workaround
There's a workaround of handing errors in a PowerShell script, for example, check exit code of commands or/and set $ErrorActionPreference = "Stop"
- is related to
-
BAM-26065 Bamboo variables are been read as unique String when setting more than one value
-
- Closed
-
- mentioned in
[BAM-21162] Better handle PowerShell command execution in Bamboo
Support reference count | New: 2 |
UIS | Original: 2 | New: 3 |
UIS | New: 2 |
Remote Link | New: This issue links to "+core+ Dogfooding › TBD Test Git Branch Detection › ktlo-BAM-21162_revertion (tardigrade-bamboo)" [ 1001610 ] |
Fix Version/s | Original: 10.2.2 [ 110830 ] | |
Fix Version/s | Original: 11.0.0 [ 110791 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Closed [ 6 ] | New: Gathering Interest [ 11772 ] |
Fix Version/s | New: 11.0.0 [ 110791 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |