Job stopping on new push?

Actions

jwalzer November 15, 2023, 10:55pm 1

So I have a workflow that triggers on [push,pull-request]
in essence nothing fancy. Just one matrix key to build for bullseye and bookworm.
One last step is a cleanup step which has an if: ${{ always() }} clause.
Works normally quite well …

But: what I’ve seen is that, while the jobs are still running, If I push another new commit to gitea, then suddenly All the running jobs of that repo get canceled and the new ones start.

This even prevents the cleanup-step from triggering, so I have to do the cleanup myself.

Question is: Is this intended behavior or should I troubleshoot, why the jobs get canceled?
So far the CI-Runner doesn’t look like it has an issue … (I’m using privileged DinD with root)

greetings

magnus_lindstrom March 25, 2024, 1:03pm 2

I’m also interested in an answer to this.

wolfogre March 26, 2024, 2:34am 3

I believe it’s related to

• Implement auto-cancellation of concurrent jobs if the event is push by appleboy · Pull Request #25716 · go-gitea/gitea · GitHub
• Cancel previous runs of the same PR automatically by wolfogre · Pull Request #29961 · go-gitea/gitea · GitHub

frd1 April 8, 2024, 6:57am 4

Also interested on this.

It’s happening both with on push and on schedule. As soon as the new push/schedule kicks in, the current job gets stopped and the new one starts.

I tried to setup a lock system, but as it stops at the same time the new one starts, it does not work.

Is there any plans to implement Github’s concurrency system?

GitHub Docs

Using concurrency - GitHub Docs

Run a single job at a time.

What is the state of this?

github.com/go-gitea/gitea

[Actions] Support concurrency syntax

opened 02:09PM - 17 May 23 UTC

lunny

type/proposal type/feature proposal/accepted topic/gitea-actions

### Feature Description simple: ```yaml concurrency: group: container-…release ``` advanced: ```yaml concurrency: group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }} cancel-in-progress: true ``` https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency

Thanks!

MarcParcerisa July 19, 2024, 10:59am 5

Also interested on this. Does anyone know if there is any way to disable this behaviour? I want all my workflow runs to finish no matter what.

achikhv October 25, 2024, 12:52am 6

I would also like some way to disable auto-cancellation. We run set of tests when commit is pushed to main. If commits are pushed frequently enough none of the jobs can run to completion.

Also there is another problem when jobs are executed directly on a host. Normally after job is completed runner cleans it’s cache. But if job is cancelled cache stays there like forever.