-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Plugin v2.21 and 2.30. Also tested this on several Jenkins of various versions.
Running a `sh()` step that has `&>` or any redirect causes the command to work even if the command should fail. It also doesn't appear that the command is running at all.
So `sh('FakeNews &> test.log')` outputs the `command not found` error to the console instead of the file. Creates an empty `test.log` and the build passes even though it should have failed. But `sh('FakeNews')` causes exception FakeNews: command not found. This is a more recent issue (last 4 months or so) didn't see this before that.
I had originally created this bug as a docker issue but I'm seeing it on our updated AWS instances as well.
[JENKINS-57149] Shell redirect causes exit code 0
Levi Blaney
created issue -
Levi Blaney
made changes -
| Summary | Original: Shell redirect causes exit code 0 on official docker Jenkins | New: Shell redirect causes exit code 0 |
Levi Blaney
made changes -
| Description |
Original:
When using the official Jenkins docker container `jenkins/jenkins` or `jenkins/jenkins:lts`, running a `sh()` step that has `&>` causes the command work even if the command should fail. It also doesn't appear that the command is running at all. So `sh('notacommand &> test.log')` outputs the `command not found` error to the console instead of the file. Creates an empty `test.log` and the build passes even though it should have failed. |
New:
Running a `sh()` step that has `&>` or any redirect causes the command to work even if the command should fail. It also doesn't appear that the command is running at all. So `sh('notacommand &> test.log')` outputs the `command not found` error to the console instead of the file. Creates an empty `test.log` and the build passes even though it should have failed. I had originally created this bug as a docker issue but I'm seeing it on our updated AWS instances as well. |
Levi Blaney
made changes -
| Description |
Original:
Running a `sh()` step that has `&>` or any redirect causes the command to work even if the command should fail. It also doesn't appear that the command is running at all. So `sh('notacommand &> test.log')` outputs the `command not found` error to the console instead of the file. Creates an empty `test.log` and the build passes even though it should have failed. I had originally created this bug as a docker issue but I'm seeing it on our updated AWS instances as well. |
New:
Running a `sh()` step that has `&>` or any redirect causes the command to work even if the command should fail. It also doesn't appear that the command is running at all. So `sh('FakeNews &> test.log')` outputs the `command not found` error to the console instead of the file. Creates an empty `test.log` and the build passes even though it should have failed. But `sh('FakeNews')` causes exception FakeNews: command not found. This is a more recent issue (last 4 months or so) didn't see this before that. I had originally created this bug as a docker issue but I'm seeing it on our updated AWS instances as well. |