Cron job runs 6 times

[FuzzyMistborn]

Figure this isn't a bug with Woodpecker but rather a me problem (switching from Drone to Woodpecker). I have a pipeline running on cron, and it ran last night but seems to have been triggered 6 times. Should have only been triggered once.

Here are the steps (it's kludgey but it works):

steps:
  - name: Check Dockerhub Nextcloud Version
    image: fuzzymistborn/docker-alpine-skopeo:latest
    commands:
      - /bin/sh ./update.sh

  - name: push
    image: drone/git
    secrets:
      - gh_api_key
      - email
      - tg_id
      - tg_token
    commands:
      - |+
        if [ $(git diff HEAD | wc -l) -gt 1 ]
        then
        git config --global user.email "$email"
        git config --global user.name "FuzzyMistborn"
        git add .
        git remote add deploy https://fuzzymistborn:[email protected]/FuzzyMistborn/nextcloud-docker.git
        DOCKER_VER=$( cat docker_ver )
        git commit -m "[CI Skip] Update Docker image to $DOCKER_VER"
        git tag -a $DOCKER_VER -m "Nextcloud Release v. $DOCKER_VER"
        git push deploy main
        git push deploy main $DOCKER_VER
        curl -s -X POST https://api.telegram.org/bot$TG_TOKEN/sendMessage -d chat_id=$TG_ID -d parse_mode=markdown -d text="✅  New Nextcloud Docker Release! %0A🌐  [Output]({{build.link}})"
        git remote rm deploy
        fi

  - name: Send TG Notification
    image: appleboy/drone-telegram
    settings:
      token:
        from_secret: tg_token
      to:
        from_secret: tg_id
      format: markdown
      message: |-
        ❌  Nextcloud Docker Updater Task has *FAILED*!
        🌐  [Output]({{build.link}})
    when:
      event: {}
      status:
        - failure

when:
  event: cron
  cron: "update"

[qwerty287]

This looks like a bug to me, I'm not aware of how you could trigger a cron multiple times.
What's the configuration of your cron? And is there something interesting in the logs?

We had a similar issue with PRs but not sure if that's related.

[FuzzyMistborn]

Ok good to know I'm not crazy then hahaha.

Cron is * * */6 * * * (running every 6 hours). I didn't see anything crazy in the logs, but I did revert to a manual push. I'll revert to cron and see if there's anything. I don't recall seeing anything odd before though.

[zc-devs]

Reproduced in Woodpecker 2.5.0, Kubernetes.

Pipeline:

skip_clone: true
steps:
  server:
    image: alpine
    commands:
      - echo Hello

Cron:

* 1/5 * * * *

Repeated 7 times:
Screenshot 1
Screenshot 2

woodpecker-server.log
woodpecker-agent.log

[qwerty287]

I'm not a cron expert, but we have seconds as the first char and doesn't * mean on every second?

Can you check what happens with 0 1/5 * * * * or 0 * */6 * * *?

[zc-devs]

0 1/5 * * * *

Works as expected

doesn't * mean on every second?

You are right

Something should definitely be improved in that space :)
#3781

[FuzzyMistborn]

Thank you all, I figured there was user error involved. 0 0 */6 * * * seems to be working.