You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have declared this as a bug, as in my opinion features should always guarantee a certain degree of backward compatibility. Especially with such cuts.
We have a lot of people working in the same branches. As our tests take approx. 10-20 minutes, one or more new pushes may be received on a branch during this time. Due to the auto-cancellation feature, we now lose the information on which commit the tests failed first. This is because all jobs are canceled if they have not yet expired.
Is there a way to deactivate this function? At workflow level or repository level?
Gitea Version
1.22.4
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
run from docker
The text was updated successfully, but these errors were encountered:
sl1zz3r
changed the title
Disable | auto-cancellation of concurrent jobs if the event is push
Disable Option | auto-cancellation of concurrent jobs if the event is push
Dec 4, 2024
Description
I am referring to the following feature:
#25716
I have declared this as a bug, as in my opinion features should always guarantee a certain degree of backward compatibility. Especially with such cuts.
We have a lot of people working in the same branches. As our tests take approx. 10-20 minutes, one or more new pushes may be received on a branch during this time. Due to the auto-cancellation feature, we now lose the information on which commit the tests failed first. This is because all jobs are canceled if they have not yet expired.
Is there a way to deactivate this function? At workflow level or repository level?
Gitea Version
1.22.4
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
run from docker
The text was updated successfully, but these errors were encountered: