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

Extend NoParallelExecution for all Triggers #46

Open
michaelschnyder opened this issue Apr 8, 2017 · 0 comments
Open

Extend NoParallelExecution for all Triggers #46

michaelschnyder opened this issue Apr 8, 2017 · 0 comments
Milestone

Comments

@michaelschnyder
Copy link
Member

Current Situation
The current implementation of NoParallelExection only guards the parellel execution if the trigger is a "Scheduled" one. That means, that a Job with a Trigger and NoParallelExecution set, does still allow running the job at the same time but with a different trigger.

Proposed Change
The NoParallelExeuction should be set on Jobs and not in a single trigger instance. The aim is to exclusively run one single instance of a job no matter with trigger or triggertype has scheduled the run.

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

No branches or pull requests

1 participant