-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Milestone
Comments
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 ? |
added support for |
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
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.
But I can't exclude some pipelines/steps from all cronjobs.
I tried to use something like
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
Thanks
The text was updated successfully, but these errors were encountered: