Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RUN-993: rd run -f exits with code 0 when job execution fails #446

Closed
manuel-espina opened this issue May 26, 2022 · 0 comments
Closed

RUN-993: rd run -f exits with code 0 when job execution fails #446

manuel-espina opened this issue May 26, 2022 · 0 comments
Labels
bug

Comments

@manuel-espina
Copy link

The behaviour of rd run -f has changed in version 2.0.0: now the exit code is 0 even if the job execution fails. In previous versions, the exit code was not 0 in that case, so an execution failure was easily detectable when launching it from a script, for example.

Is this an intended change? Could the previous behaviour be restored (either by default or by specifying an option)?
@gschueler gschueler added the bug label Jun 15, 2022
@gschueler gschueler changed the title rd run -f exits with code 0 when job execution fails RUN-993: rd run -f exits with code 0 when job execution fails Jun 15, 2022
gschueler added a commit that referenced this issue Jun 21, 2022
@gschueler
Merge pull request #455 from rundeck/issue/446-run-993--rd-run--f-exi…
4ddb6ea 
…ts-with-code-0-when-job-execution-fails

RUN-993: Fix #446 exit code should not be 0 when run -f execution fails
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gschueler @manuel-espina