-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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.
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
rerunning all jobs no longer respects what needs what #27884
Labels
Milestone
Comments
This comment has been minimized.
This comment has been minimized.
Same issue here. I've prepared a lighter workflow to reproduce the bug: # Since the default value of act_runner "fetch_interval" parameter is
# "10s", we need to sleep each step for > 10secs...
name: Test
run-name: ${{ gitea.actor }} started this build
on:
push:
jobs:
job1:
name: job1
steps:
- name: job1 step
run: |
sleep 15
echo "job1 done!"
job2:
name: job2
steps:
- name: job2 step
run: |
sleep 15
echo "job2 done!"
job3:
name: job3 (waits for both job1 and job2)
needs: [ job1, job2 ]
steps:
- name: job3 step
run: |
sleep 15
echo "job 3 done!" |
Bug is still present in Gitea 1.21.4 |
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Mar 22, 2024
Fix go-gitea#28761 Fix go-gitea#27884 Fix go-gitea#28093 ## Changes ### Rerun all jobs When rerun all jobs, status of the jobs with `needs` will be set to `blocked` instead of `waiting`. Therefore, these jobs will not run until the required jobs are completed. ### Rerun a single job When a single job is rerun, its dependents should also be rerun, just like GitHub does (go-gitea#28761 (comment)). In this case, only the specified job will be set to `waiting`, its dependents will be set to `blocked` to wait the job. ### Show warning if every job has `needs` If every job in a workflow has `needs`, all jobs will be blocked and no job can be run. So I add a warning message. <img src="https://github.com/go-gitea/gitea/assets/15528715/88f43511-2360-465d-be96-ee92b57ff67b" width="480px" />
lunny
added a commit
that referenced
this issue
Mar 22, 2024
Backport #29955 by @Zettat123 Fix #28761 Fix #27884 Fix #28093 ## Changes ### Rerun all jobs When rerun all jobs, status of the jobs with `needs` will be set to `blocked` instead of `waiting`. Therefore, these jobs will not run until the required jobs are completed. ### Rerun a single job When a single job is rerun, its dependents should also be rerun, just like GitHub does (#28761 (comment)). In this case, only the specified job will be set to `waiting`, its dependents will be set to `blocked` to wait the job. ### Show warning if every job has `needs` If every job in a workflow has `needs`, all jobs will be blocked and no job can be run. So I add a warning message. <img src="https://github.com/go-gitea/gitea/assets/15528715/88f43511-2360-465d-be96-ee92b57ff67b" width="480px" /> --------- Co-authored-by: Zettat123 <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Mar 22, 2024
Fix go-gitea#28761 Fix go-gitea#27884 Fix go-gitea#28093 ## Changes ### Rerun all jobs When rerun all jobs, status of the jobs with `needs` will be set to `blocked` instead of `waiting`. Therefore, these jobs will not run until the required jobs are completed. ### Rerun a single job When a single job is rerun, its dependents should also be rerun, just like GitHub does (go-gitea#28761 (comment)). In this case, only the specified job will be set to `waiting`, its dependents will be set to `blocked` to wait the job. ### Show warning if every job has `needs` If every job in a workflow has `needs`, all jobs will be blocked and no job can be run. So I add a warning message. <img src="https://github.com/go-gitea/gitea/assets/15528715/88f43511-2360-465d-be96-ee92b57ff67b" width="480px" />
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
when I re run all jobs in a workflow (from the ui) after one has failed the structure of what needs what is not respected - ie they all run at once.
The original run respects structure.
my workflow is as below fwiw
Gitea Version
1.21.0-rc2
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
ubuntu
How are you running Gitea?
container from docker hub on linux
Database
SQLite
The text was updated successfully, but these errors were encountered: