-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Labels
new featurenew featurenew featurepluginrelated to the multi-factor priority pluginrelated to the multi-factor priority plugin
Description
The priority plugin will need to do two separate things concerning preemptible-after attributes for a job:
- If an association does not set a
preemptible-afterattribute for their job and they are running under a special bank that hasmax-preemptible-afterconfigured, the job should be updated to include this attribute. This could probably happen in the callback forjob.new, where default bank and default project name jobspec-updates are also currently happening. - If an association does set a
preemptible-afterattribute for their job, it should be validated to make sure that the value is not greater than themax-preemptible-aftervalue set for the bank. If it is, it should automatically be lowered to whatever the max is. I'm thinking this could probably also happen in the callback forjob.newsince jobs won't be rejected in case the value is too high, it'll just be updated.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
new featurenew featurenew featurepluginrelated to the multi-factor priority pluginrelated to the multi-factor priority plugin