Job runs even if previous job failed - and "success() == true" ! #81
Consider this workflow:
jobs: d_update_services: name: Test Services runs-on: ubuntu-latest steps: - name: Details run: echo "error" && exit 1 z_complete: name: Complete Job runs-on: ubuntu-latest needs: d_update_services steps: - name: Details run: | echo "User: $(whoami)" echo "Shell: $SHELL" echo $BASH_VERSION ls -l $(which sh) echo "" echo "GITHUB_OUTPUT = $GITHUB_OUTPUT" echo "GITHUB_STEP_SUMMARY = $GITHUB_STEP_SUMMARY" - name: Job Succeeded if: success() run: | echo "Success" - name: Job Failed if: failure() run: | echo "Failure" - name: Job Canceled if: cancelled() run: | echo "Cancelled"
In GitHub Actions, the behavior is this:
In Gitea Actions, the behavior is this:
If all the steps are in the same job, the "failure() = true", which is the expected and as per the GitHub Actions.
But if they are different jobs (as per my YAML above), with the "needs", the second job should be Skipped.
If the "needs" isn't present, then GitHub Actions runs the other job, and also makes "success() = true".
So, "success()" seems to be just per Job, and not per "Run/Workflow".
I believe the bug here, then, is just that "needs" is being ignored in Gitea Actions.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?