Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinct event trigger for Cron pipelines #2705

Closed
chromko opened this issue May 13, 2019 · 2 comments
Closed

Distinct event trigger for Cron pipelines #2705

chromko opened this issue May 13, 2019 · 2 comments
Milestone

Comments

@chromko
Copy link

chromko commented May 13, 2019

I can't skip some pipelines/steps during cron scheduling.
When I use cron jobs, I can set pipeline trigger with cronjob name to include this pipline during cron execution.

trigger:
  cron: ['cron']

But I can't exclude some pipelines/steps from all cronjobs.
I tried to use something like

trigger:
  cron: 
    exclude: '*'

to exclude cronjobs from common pipelines for pushing code to repo.
But when i commit to repo, I'm getting trigger: skipping pipeline, does not match cron job.

It would be nice to add event type 'cron' to avoid this problem.
I think it'll look like

trigger:
  event: 
    exclude: 'cron'

Thanks

@bradrydzewski bradrydzewski added this to the v1.x.x milestone May 21, 2019
@random-ua
Copy link

I noticed that DRONE_COMMIT_BEFORE and DRONE_SOURCE_BRANCH are empty when build is triggered by cron. Could this be used to reliably distinguish between regular builds and cron-triggered ones ? Or this is something that will be changed in future versions ?

@bradrydzewski
Copy link

added support for event: cron in master.

ErwinJanssen added a commit to tlsprint/models that referenced this issue Dec 17, 2019
Without the promote event, cron will end up in the actual configuration.
This can be tested by running the 'drone fmt' command on the .drone.yml
file. Also mentioned here: harness/harness#2705
bot2-harness pushed a commit that referenced this issue Sep 24, 2024
…reuse in harness-code, update router (#2705)

* feat: [AH-295]: add STO details in AR summary api - rebase
* feat: [AH-295]: add STO details in AR summary api - handle errors
* feat: [AH-295]: add STO details in AR summary api - lint error
* feat: [AH-295]: add STO details in AR summary api - refactor code to reuse in harness-code, update router
* feat: [AH-295]: add STO details in AR summary api - refactor code to reuse in harness-code, update router
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants