-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add possibility to provide a priorization strategy for jobruns #4
Comments
This also relates to Jira SPPLAT-398, where an immediately run of a instant trigger is requested, See: Current Situation New Situation Acceptance Criteria |
We could support this on different levels
Or by isolating the current PriorizationLogic in a separate class that can be passed to the default Schedulers Configuration like public class CustomPriorizationStrategy : IPriorizationStrategy
{
public int CompareTo(JobRunAndJobAndTrigger first, JobRunAndJobAndTrigger second)
{
return 1;
}
} As discussed with @olibanjoli, we will first implement the proposed alternative to keep the flexibility for different scenarios. This implementation is also required for jobbrIO/jobbr-webapi#11 |
@samuelmeierzuehlke: Item will be moved to Version 1.1 |
This feature is requested from one of our projects.
They would like to prioritize manual triggered jobs higher than monthly/daily triggered jobs.
We probably don't need this information in the database itself, it might by enough when we just could give the Scheduler a hint how the plan should be ordered by an additional configuration.
Source: @samuelmeierzuehlke
The text was updated successfully, but these errors were encountered: