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.

Sign up for GitHub

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

Jump to bottom

Add support for sequential job definitions #854

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add support for sequential job definitions #854

wants to merge 3 commits into from

Commits on Jul 31, 2024

  1. Override global option with group option 

    Local options override globally set options, but options set on the `every` group do not.

It makes sense for the options defined closer to the actual job to override those set further away, so we change the merge order of options to allow options passed to `every` to override those set globally with `set`. We still allow local options set on each job to override those set on the group.
    @njakobsen
    njakobsen committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    82986a1 View commit details
    Browse the repository at this point in the history

  2. Add support for sequential job definitions 

    Jobs now support a `sequence` option that will cause jobs with the same `sequence` value to run sequentially when scheduled for the same time. `sequential: true` can be passed to the `every` block to automatically set a common `sequence` value for each contained job.

Closes javan#19
Closes javan#696
Closes javan#835
    @njakobsen
    njakobsen committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    1136104 View commit details
    Browse the repository at this point in the history

  3. Allow sequential jobs to continue by default 

    It's likely that since jobs ran in parallel before, there were no dependencies between jobs. Therefore, now that sequential jobs are possible, we should continue execution of the job sequence even if one job fails. To override this and halt the sequence on failure, individual jobs can set `halt_sequence_on_failure: true` to suffix their command with an "&&" instead of a ";".
    @njakobsen
    njakobsen committed Jul 31, 2024
    Configuration menu
    Copy the full SHA
    6a4c748 View commit details
    Browse the repository at this point in the history