Cron utils for parsing, validations and human readable descriptions as well as date/time interoperability.
@/all New release available! Details available here Many thanks to @Naxos84 @SvenssonWeb @rhanton @jpotts2 @tanyona @meincs @curioustechizen ! :smile:
for my android project?
bdw thanks @jmrozanec
and of course also :+1: for all contributors!
@garganshu I would suggest to check the snippet for the corresponding version at mvn-repository You will find snippets on how to declare the dependency for various dependency managers (for Android you will be most probably using Gradle) Let us know if you need further help on this. Best!
@/all we received jmrozanec/cron-utils#318 if would be possible to handle multiple crons in a single expression. We commented on how this could be achieved when building a string pattern and started developing the feature in a branch. We would be glad to hear opinions and suggestions regarding the feature and its implementation.
@/all multi-cron support is implemented! A new release will follow this weekend! We are working on how to provide better human readable descriptions and experimenting if some machine learning can be applied to achieve it. If anyone would like to jump in, is welcome to do so! The reference issue will be jmrozanec/cron-utils#3
Hi,
My company has a spring-boot micro-service applications, and I am looking for a jobs which can perform "git pull", "git pull before push". Is there any way to write such jobs for Java applications (btw we're using GITLAB as a SCM), I know that there is cron API for PHP applications, is there any such thing for Java applications also?
My company has a spring-boot micro-service applications, and I am looking for a jobs which can perform "git pull", "git pull before push". Is there any way to write such jobs for Java applications (btw we're using GITLAB as a SCM), I know that there is cron API for PHP applications, is there any such thing for Java applications also?
@/all New release available! Details available here Many thanks to @hokkun-dayo @catharsis @Naxos84 @kangtajt007 @SvenssonWeb @mattadamson @TuomasKiviaho @alenkacz @kensipe @roddy @toby1984 @morvael @francisdb @MrKulp for reporting issues, discussing them and submitting PRs with fixes and features. The new release includes an updated Dutch translation, bugfixes such as avoid an infinite loop when seeking impossible dates, truncation at milliseconds level when computing past executions; and features such as workdays computation for next/past executions, support for multiple cron expressions in a single expression and crons serialization.
Hi @/all ! We are working towards providing much better cron descriptions using machine learning methods. We already have a working model for English language, which we hope to release within a month. In order to support the rest of the languages, we require to generate datasets with examples for each of them. To achieve it, we coded some generators, which create valid samples based on some descriptions. Help to code dataset generators for the rest of the languages will be highly appreciated. We are tracking the issue under #3 and coding the generators at this repo: https://github.com/jmrozanec/cron-utils-datagen Thanks! :smile:
Hi team, thanks so much for your work on this wonderful utility! I am just running into a problem: I am creating a Cron object from this expression "0 0 ? 7-1 *". When I try to find the last execution time by calling ExecutionTime.lastExecution(now), it gets stuck. I can see in SingleExecutionTime.potentialPreviousClosestMatch() method it keeps going to last day of previous month looking for a potential match. This should not be the case. The description of the above expression is correctly given as "every hour every day between Saturday and Sunday". Any assistance would be appreciated!
@ctonsing Hi! thank you for reaching out! May we ask you for some more code in order to reproduce the issue? Are you using quartz/unix/... format? Which version of the utility do you use? We just released version 7.0.4 which fixes an issue regarding infinite loops while looking for a match. Thanks!
@jmrozanec Thank you very much for your response! I am indeed using v7.0.4
My pom.xml includes:
<dependency>
<groupId>com.cronutils</groupId>
<artifactId>cron-utils</artifactId>
<version>7.0.4</version>
</dependency>The code you can use to replicate the problem is as follows (sorry, I see I copied the schedule expression incorrectly in my previous message...):
String schedule = "0 0 * ? * SAT-SUN *";
CronParser parser = new CronParser(cronDefinition);
Cron quartzCron = parser.parse(schedule);
CronDescriptor descriptor = CronDescriptor.instance();
String description = descriptor.describe(quartzCron);
System.out.println(description);
ZonedDateTime time = ZonedDateTime.now();
ExecutionTime executionTime = ExecutionTime.forCron(quartzCron);
// Time from last execution to now
Duration timeFromLastExecution = executionTime.timeFromLastExecution(time).get();
System.out.println(timeFromLastExecution.toMinutes());
@jmrozanec I believe the problem is probably in the com.cronutils.model.time.generator.BetweenDayOfWeekValueGenerator(CronField cronField, int year, int month, WeekDay mondayDoWValue) constructor. Since the schedule expression is "SAT-SUN", the constructor's "from" variable is 7 and the "to" variable is 1, which means the body of the for loop is never entered...
@/all new version 7.0.6 was released! Many thanks to @pkoenig10 @minidmnv @charleshope @cbgxhub @soriniulus @Naxos84 for reporting and fixing issues! The release solves an infinite loop issue when computing previous/next date as well as fixes issues with custom cron definitions with 3 fields. We also thank @chbakouras for providing us with Greek locales: we can now read descriptions in Greek language!
@/all with all these improvements we also reached 1K commits! :smile:
Hi, I'm trying to understand how to use the parser in order to compute next execution based on the last execution.
is this code should work?
ZonedDateTime lastExecution = ZonedDateTime.ofInstant(new Date(entity.getEndTime()).toInstant(), ZoneId.systemDefault());
executionTime.lastExecution(lastExecution);
ZonedDateTime now = ZonedDateTime.now();
final long millis = executionTime.timeToNextExecution(now).get().toMillis();
@avico927_gitlab here a gist with a working implementation: https://gist.github.com/jmrozanec/5d5554bd47a94ad42807547e0948d7dc
Please let us know if further help is needed! :smile: Best!
@/all we are happy to announce a new cron-utils release with new features and multiple bugfixes :smile: Thanks to everyone who made it possible: @josephtaylor @thebhushanp @palerique @ph-redknee @robryals @pgorin @tubean @NielsDoucet @toughpheeckouse
Hello, I think that I've hit into a bug. When using Quartz to express every n years starting in year X, on a particular day, lastExecution is incorrect. (if you even do isMatch on what it generates, it produces false). Even doing lastExecution on what's generated from nextExecution generates an incorrect result.