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

Cron triggers #8

Closed
laszlocph opened this issue Apr 5, 2019 · 5 comments · Fixed by #934
Closed

Cron triggers #8

laszlocph opened this issue Apr 5, 2019 · 5 comments · Fixed by #934
Assignees
Labels
feature add new functionality
Milestone

Comments

@laszlocph
Copy link
Member

Implement cron like triggers to enable nightly builds.

@6543 6543 added the feature add new functionality label Jun 23, 2021
@6543
Copy link
Member

6543 commented Jun 23, 2021

drone example:
Bildschirmfoto zu 2021-06-23 16-13-54

I also would add a manual "play-button" to trigger it manually next to delete icon

@anbraten anbraten added this to the 0.16.0 milestone Oct 17, 2021
@6543 6543 self-assigned this Feb 1, 2022
@mscherer mscherer mentioned this issue May 20, 2022
21 tasks
@mscherer
Copy link
Contributor

So, what would be the syntax for the cron jobs ?

I see several choices:

  • have 1 string and reuse the format from vixie cron (eg "5 0 * * *"). While this is well known and compact (and I think easy to parse), I think it tend to be error prone. For example, the example I typed is "running 5 minutes after midnight", but I would have guessed it was "running at 5 in the morning". There is a module for that, do not look maintained.
  • have 1 string, and reuse systemd syntax. This is the one that linux sysadmin would known now, and I think it is better than the cron one (more flexible, more intuitive). But it is a lot more complex, it is more verbose and the question become on whether the format should "calendar event", or "duration", or both. Do we want to say "run that every X minutes/hours/duration", or "run at time that match this pattern". There is a module, also maybe unmaintained.
  • do a custom format. This could mean to not limit the format to "schedule: xxxx", and have a custom DSL in yaml.

@6543
Copy link
Member

6543 commented May 20, 2022

https://pkg.go.dev/github.com/robfig/cron?utm_source=godoc#hdr-Usage

@svdHero
Copy link

svdHero commented Jun 8, 2022

This feature is crucial for us, since we also want to execute long running nightly system tests with Woodpecker.

@anbraten anbraten mentioned this issue Jul 1, 2022
31 tasks
@6543
Copy link
Member

6543 commented Aug 28, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature add new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants