ci: fix cron job for auto tagging#574
Conversation
Fix the trigger for the auto tagging job. At the moment it would run on every day of January instead of every 1st of each month. Here is the format: ``` ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of the month (1 - 31) │ │ │ ┌───────────── month (1 - 12 or JAN-DEC) │ │ │ │ ┌───────────── day of the week (0 - 6 or SUN-SAT) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ * * * * * ```
| # Run every month on the 1st day at 08:15 AM. | ||
| - cron: '15 8 * 1 *' | ||
| # Run every month on the 3rd day at 08:15 AM. | ||
| - cron: '15 8 3 * *' |
There was a problem hiding this comment.
Changed the schedule from the 1st of the month to 3rd of the month, as I hope this fix gets approved and merged, before this possible next schedule and we see it in action.
And as we are supposed to provide a tagged version for OTel collector release, tagging should happen rather soonish.
|
How about adding a |
I was looking into this, but couldn't find a proper way to limit it to a user group. Ideally only maintainers (or approvers) of the project should be able to trigger a workflow_dispatch run to tag a new version. As I didn't find anything around authorization for this kind of trigger, I did not add it. |
|
Only folks with write permissions should be able to trigger a workflow. |
Signed-off-by: Florian Lehner <florian.lehner@elastic.co>
I wasn't aware of that and obviously didn't find any documentation around it. Added the manual trigger with 08dfef9. |
|
From the doc above:
|
|
Thanks @christos68k for merging. In other words - please cheer for our first tag: https://github.com/open-telemetry/opentelemetry-ebpf-profiler/tags |
🎉 |
Fix the trigger for the auto tagging job. At the moment it would run on every day of January instead of every 1st of each month.
Here is the format: