Webhook: Another job is still in progress for this repository

[la7eralus]

Description

Hello,
I constantly get the error "Another job is still in progress for this repository" when triggering the deployment via webhook. Luckily it does deploy the stack just fine, so the only problem is the notification send and the error in the logs.

<---STARTUP--->
{"time":"2025-12-06T01:08:07.642386272+01:00","level":"info","msg":"starting application","version":"v0.54.0","log_level":"info"}
{"time":"2025-12-06T01:08:07.652166151+01:00","level":"info","msg":"api endpoints disabled, no api secret configured"}
{"time":"2025-12-06T01:08:07.65218829+01:00","level":"info","msg":"listening for events","http_port":80,"enabled_endpoints":["/v1/health","/v1/webhook"]}
{"time":"2025-12-06T01:08:07.652304666+01:00","level":"info","msg":"serving prometheus metrics","http_port":9120,"path":"/metrics"}
<---RENOVATE CREATES BRANCH webhook_filter: refs/heads/main--->
{"time":"2025-12-06T01:08:51.000265126+01:00","level":"info","msg":"received new job","job_id":"019af0fd-6a37-786d-8017-9c28dff7853a","repository":"github.com/myrepo/compose","custom_target":"alpine","trigger":{"commit":"dbcba5322914065ea7702fc6bf9136df2e7f5d75","ref":"refs/heads/renovate/adguard-adguardhome-0.x","event":"webhook"}}
{"time":"2025-12-06T01:08:51.391261299+01:00","level":"info","msg":"job completed successfully","job_id":"019af0fd-6a37-786d-8017-9c28dff7853a","repository":"github.com/myrepo/compose","custom_target":"alpine","elapsed_time":"390ms"}
<---AUTOMERGE TO MAIN webhook_filter: refs/heads/main--->
{"time":"2025-12-06T01:08:55.525382717+01:00","level":"info","msg":"received new job","job_id":"019af0fd-7be5-73c8-a410-3c53ab73c407","repository":"github.com/myrepo/compose","custom_target":"alpine","trigger":{"commit":"b45a99e3122940e2f8bd549dcc917c6f9c9e2d80","ref":"refs/heads/main","event":"webhook"}}
{"time":"2025-12-06T01:08:56.007473036+01:00","level":"info","msg":"deploying stack","job_id":"019af0fd-7be5-73c8-a410-3c53ab73c407","repository":"github.com/myrepo/compose","custom_target":"alpine","stack":"adguardhome","reference":"refs/heads/main","repository":"github.com/myrepo/compose","stack":"adguardhome","forced":false}
{"time":"2025-12-06T01:08:56.157468465+01:00","level":"error","msg":"Another job is still in progress for this repository","job_id":"019af0fd-7e5d-75a3-bdfe-2d09301a272f"}
{"time":"2025-12-06T01:09:01.008213469+01:00","level":"info","msg":"deployment in progress","job_id":"019af0fd-7be5-73c8-a410-3c53ab73c407","repository":"github.com/myrepo/compose","custom_target":"alpine","stack":"adguardhome","reference":"refs/heads/main","repository":"github.com/myrepo/compose","stack":"adguardhome"}
{"time":"2025-12-06T01:09:02.758287192+01:00","level":"info","msg":"job completed successfully","job_id":"019af0fd-7be5-73c8-a410-3c53ab73c407","repository":"github.com/myrepo/compose","custom_target":"alpine","elapsed_time":"7.232s"}
<---RENOVATE CREATES BRANCH webhook_filter: refs/heads/main--->
{"time":"2025-12-06T01:09:11.00399093+01:00","level":"info","msg":"received new job","job_id":"019af0fd-b85b-71de-8284-349f25a57c05","repository":"github.com/myrepo/compose","custom_target":"alpine","trigger":{"commit":"70751e1d6c70ab402f52e503ca81e80c8fe88d4f","ref":"refs/heads/renovate/ghcr.io-paperless-ngx-paperless-ngx-2.x","event":"webhook"}}
{"time":"2025-12-06T01:09:11.322922493+01:00","level":"info","msg":"job completed successfully","job_id":"019af0fd-b85b-71de-8284-349f25a57c05","repository":"github.com/myrepo/compose","custom_target":"alpine","elapsed_time":"318ms"}
<---AUTOMERGE TO MAIN webhook_filter: refs/heads/main--->
{"time":"2025-12-06T01:09:15.291100771+01:00","level":"info","msg":"received new job","job_id":"019af0fd-c91a-7e8d-b11d-ef0cdb8ebc41","repository":"github.com/myrepo/compose","custom_target":"alpine","trigger":{"commit":"144d5ac11a3f75919fd856b717995798787f6238","ref":"refs/heads/main","event":"webhook"}}
{"time":"2025-12-06T01:09:15.454910258+01:00","level":"error","msg":"Another job is still in progress for this repository","job_id":"019af0fd-c9be-79e1-b187-e1fb5cd666ce"}
{"time":"2025-12-06T01:09:15.762200021+01:00","level":"info","msg":"deploying stack","job_id":"019af0fd-c91a-7e8d-b11d-ef0cdb8ebc41","repository":"github.com/myrepo/compose","custom_target":"alpine","stack":"adguardhome","reference":"refs/heads/main","repository":"github.com/myrepo/compose","stack":"adguardhome","forced":false}
{"time":"2025-12-06T01:09:17.138637975+01:00","level":"info","msg":"job completed successfully","job_id":"019af0fd-c91a-7e8d-b11d-ef0cdb8ebc41","repository":"github.com/myrepo/compose","custom_target":"alpine","elapsed_time":"1.847s"}

Steps to reproduce the issue

1. Set Webhook Secret and Apprise
2. Update Stack in Upstream Repo
3. See error in Log/Notification

Operating System

Linux

Docker Compose File

doco-cd:
    container_name: doco-cd
    image: ghcr.io/kimdre/doco-cd:0.54.0
    restart: unless-stopped
    ports:
      - 10200:80
    environment:
      TZ: Europe/Berlin
      LOG_LEVEL: info
      DOCKER_HOST: tcp://docker-socket-proxy:2375
      SOPS_AGE_KEY_FILE: /run/secrets/sops_age_key
      WEBHOOK_SECRET: ${WEBHOOK_SECRET}
      GIT_ACCESS_TOKEN: ${GIT_ACCESS_TOKEN}
      APPRISE_API_URL: http://apprise:8000/notify
      APPRISE_NOTIFY_LEVEL: success
      APPRISE_NOTIFY_URLS: tgram://${TELEGRAM_BOT_TOKEN}/${TELEGRAM_CHAT_ID}
    secrets:
      - sops_age_key
    volumes:
      - /opt/docker/doco-cd/data:/data
      #Y STILL NEEDED?
      - /var/run/docker.sock:/var/run/docker.sock
    healthcheck:
      test: [ "CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:80/v1/health" ]
      start_period: 15s
      interval: 30s
      timeout: 5s
      retries: 3
    depends_on:
      - apprise
      - docker-socket-proxy

secrets:
  sops_age_key:
    file: /opt/docker/doco-cd/keys.txt

networks:
  default:
    name: services

Deployment Config

working_dir: alpine/stacks
auto_discover: true
webhook_filter: refs/heads/main

Logs

[kimdre]

Check the webhook events in your SCM/Git provider. It seems like doco-cd receives multiple events for the same merge request. Most likely one for the merged MR and also for the push to main (The job_id is different in the error message). Doco-cd blocks multiple events for the same repository to prevent that these events interfere with each other during the deployment process.

[la7eralus]

Thanks for replying so fast, you are right, there are 3 Webhooks sent for the second event:

<---RENOVATE CREATES BRANCH webhook_filter: refs/heads/main--->
{"time":"2025-12-06T01:09:11.00399093+01:00","level":"info","msg":"received new job","job_id":"019af0fd-b85b-71de-8284-349f25a57c05","repository":"github.com/myrepo/compose","custom_target":"alpine","trigger":{"commit":"70751e1d6c70ab402f52e503ca81e80c8fe88d4f","ref":"refs/heads/renovate/ghcr.io-paperless-ngx-paperless-ngx-2.x","event":"webhook"}}
{"time":"2025-12-06T01:09:11.322922493+01:00","level":"info","msg":"job completed successfully","job_id":"019af0fd-b85b-71de-8284-349f25a57c05","repository":"github.com/myrepo/compose","custom_target":"alpine","elapsed_time":"318ms"}
<---AUTOMERGE TO MAIN webhook_filter: refs/heads/main--->
{"time":"2025-12-06T01:09:15.291100771+01:00","level":"info","msg":"received new job","job_id":"019af0fd-c91a-7e8d-b11d-ef0cdb8ebc41","repository":"github.com/myrepo/compose","custom_target":"alpine","trigger":{"commit":"144d5ac11a3f75919fd856b717995798787f6238","ref":"refs/heads/main","event":"webhook"}}
{"time":"2025-12-06T01:09:15.454910258+01:00","level":"error","msg":"Another job is still in progress for this repository","job_id":"019af0fd-c9be-79e1-b187-e1fb5cd666ce"}
{"time":"2025-12-06T01:09:15.762200021+01:00","level":"info","msg":"deploying stack","job_id":"019af0fd-c91a-7e8d-b11d-ef0cdb8ebc41","repository":"github.com/myrepo/compose","custom_target":"alpine","stack":"adguardhome","reference":"refs/heads/main","repository":"github.com/myrepo/compose","stack":"adguardhome","forced":false}
{"time":"2025-12-06T01:09:17.138637975+01:00","level":"info","msg":"job completed successfully","job_id":"019af0fd-c91a-7e8d-b11d-ef0cdb8ebc41","repository":"github.com/myrepo/compose","custom_target":"alpine","elapsed_time":"1.847s"}

I configured the GitHub webhook to trigger on push events only, as recommended. The first two events are sent because Renovate creates and deletes its branch — both actions count as push events in GitHub. The third event is the actual merge into main. There’s probably no way to prevent GitHub from sending these.

Would it be possible for doco-cd to apply the webhook filter before detecting, that there is already a repo job running?

If not, I guess I have to fundamentaly change how I use renovate (maybe don't use automerge).
This is my current config:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:recommended",
    ":approveMajorUpdates",
    ":automergeDigest",
    ":automergeMinor",
    ":skipStatusChecks"
  ],
  "dependencyDashboardLabels": ["dependencies"],
  "labels": ["dependencies"],
  "timezone": "Europe/Berlin",
  "reviewers": ["la7eralus"],
  "assignAutomerge": true,
  "minimumReleaseAge": "3 days",
  "packageRules": [
    {
      "matchPackageNames": ["renovate/renovate"],
      "assignAutomerge": false,
      "minimumReleaseAge": null
    },
    {
      "matchPackageNames": ["ghcr.io/immich-app/postgres"],
      "enabled": false
    }
  ]
}

[kimdre]

Would it be possible for doco-cd to apply the webhook filter before detecting, that there is already a repo job running?

Unfortunately this is not possible because doco-cd has to fetch the deployment config via the webhook payload for the webhook filter to use. I could however disable this notification and only log the error to the container logs.
Alternatively, I could extend the webhook filter by allowed event types to receive, but I haven't looked into whether that's feasible. Nevermind, Github uses the same push event type for all three events.

You could disable the webhook in the settings and trigger your own webhook from a Github actions workflow. Like that you can control it better when a webhook gets send. Someone already did the same, see here: #798 (reply in thread)

[la7eralus]

Ah okay, I see. I’ll definitely take a look at the action, but it almost seems like overkill for my problem :-) If it’s not too much trouble, it would be helpful for me not to receive a notification in that case.