[solved] Cron: skipping build, no matching pipelines

Drone Support
1

Hi,

we set up a drone crone pipeline:

trigger:
  event:
    - cron
  cron:
    - daily

Log on server shows:

{"branch":"master","cron":"allscreenshots","level":"warning","msg":"cron: trigger build","repo":"nextcloud/android","sha":"eaf1230d2e4b1cc0c10faf32fa1076f700dde680","time":"2022-01-13T00:21:42Z"}
{"commit":"eaf1230d2e4b1cc0c10faf32fa1076f700dde680","event":"cron","level":"info","msg":"trigger: skipping pipeline, does not match event","pipeline":"tests-stable","ref":"refs/heads/master","repo":"nextcloud/android","time":"2022-01-13T00:21:42Z"}
{"commit":"eaf1230d2e4b1cc0c10faf32fa1076f700dde680","event":"cron","level":"info","msg":"trigger: skipping pipeline, does not match event","pipeline":"tests-master","ref":"refs/heads/master","repo":"nextcloud/android","time":"2022-01-13T00:21:42Z"}
{"commit":"eaf1230d2e4b1cc0c10faf32fa1076f700dde680","event":"cron","level":"info","msg":"trigger: skipping pipeline, does not match event","pipeline":"analysis","ref":"refs/heads/master","repo":"nextcloud/android","time":"2022-01-13T00:21:42Z"}
{"commit":"eaf1230d2e4b1cc0c10faf32fa1076f700dde680","event":"cron","level":"info","msg":"trigger: skipping pipeline, does not match cron job","pipeline":"allScreenshots","ref":"refs/heads/master","repo":"nextcloud/android","time":"2022-01-13T00:21:42Z"}
{"commit":"eaf1230d2e4b1cc0c10faf32fa1076f700dde680","event":"cron","level":"info","msg":"trigger: skipping build, no matching pipelines","pipeline":"allScreenshots","ref":"refs/heads/master","repo":"nextcloud/android","time":"2022-01-13T00:21:42Z"}

I understand that first 3 pipelines do not match, but what about last two commit warnings?
Why does this says “does not match cron” or skipping build due to “not matching pipeline”?

Can you help me to understand the issue?

I followed:
https://docs.drone.io/pipeline/triggers/#by-cron
https://docs.drone.io/cron/

Server says:
drone cron info nextcloud/android allscreenshots
allscreenshots
Expr: @daily
Next: 2022-01-14 01:00:00 +0100 CET

2

based on the logs, it looks like your cron job is named “allscreenshots” but you have configured your yaml to only trigger when the cronjob name is “daily”

trigger:
    event:
    - cron
    cron:
-   - daily
+   - allscreenshots
3

Hi,

thanks for your fast reply!
Indeed I did this wrong, now it is working.

Many thanks!

4