Skip to content

Releases: netlogix/Netlogix.JobQueue.Scheduled

1.3.0 - Add option to keep failed jobs after reaching their numberOfRetries

19 Jun 15:47
925210e
Compare
Choose a tag to compare

What's Changed

  • Build(deps): Bump actions/checkout from 3 to 4 by @dependabot in #12
  • feat: Add option to keep failed jobs after reaching their numberOfRetries by @paxuclus in #15

Full Changelog: 1.2.4...1.3.0

1.2.4 - Make phpunit dataProviders static

26 Jun 13:54
5d061df
Compare
Choose a tag to compare

What's Changed

  • BUGFIX: Make phpunit dataProviders static by @paxuclus in #11

Full Changelog: 1.2.3...1.2.4

1.2.3 - Add missing return type hints to doctrine migrations

08 Dec 13:27
562be05
Compare
Choose a tag to compare

What's Changed

  • BUGFIX: Add return type hint to migration methods by @nlx-lars in #10

Full Changelog: 1.2.2...1.2.3

1.2.2 - Calculate DateInterval in tests based on Now

24 Aug 13:19
a9447e3
Compare
Choose a tag to compare

The retry test expects a certain number of seconds between the
initial scheduling and the retry value.

To have a human readable understanding of how long a retried
command should be deferred in contrast to how long it is actually
defered (that's what retry test does), the test doesn't work on
number of seconds but on a PHP DateInterval object.

The internal data structure of that date interval object is based
on the current time zone because 3276800 seconds are always 37.9
days on one hand, but either 1 month and 6 days or 1 month and 7
days on the other, depending on which month the value should be
added to.

1.2.1 - Release expired jobs

07 Jul 09:31
Compare
Choose a tag to compare

Re-scheduling did not increase incarnation count. Even if it did, expired jobs would still be present in the database, although marked as claimed and hence invisible for polling.

1.2.0 - Retry with backoff strategy

06 Jul 14:11
f415cab
Compare
Choose a tag to compare

Allow jobs to only retry a certain amount of times.
Back off either a fixed number of seconds or an exponentially increasing number of seconds, depending on configuration.

The poll command used to retry failed jobs immediately right after the current batch was finished and kept on retrying indefinitely.
For compatibility reasons, that's still the behavior, which is achieved by a numberOfRetries of -1, a backoffStrategy set to "linear" and a retryInterval of 0.

1.0.1 - Add support for Flow ^7.3 and ^8.0

19 May 09:57
c4d43ee
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.0.0...1.0.1

1.0.0 - Initial Release

13 May 08:03
cb94fb1
Compare
Choose a tag to compare

What's Changed

  • TASK: Remove version from composer.json by @tweis in #1
  • Feature/GitHub actions by @nlx-lars in #3
  • FEATURE: Add support for FLOW 6 by @tweis in #2
  • Build(deps): Bump actions/checkout from 2 to 3 by @dependabot in #5
  • Build(deps): Bump actions/cache from 1 to 3 by @dependabot in #4

New Contributors

Full Changelog: https://github.com/netlogix/Netlogix.JobQueue.Scheduled/commits/1.0.0