-
Notifications
You must be signed in to change notification settings - Fork 929
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
Flag for success when node filter does not match any node #2456
Conversation
@@ -67,6 +68,7 @@ public class BaseNodeFilters { | |||
nodeIncludeOsVersion(nullable: true) | |||
nodeExcludeOsVersion(nullable: true) | |||
nodeExcludePrecedence(nullable: true) | |||
//successOnEmptyNodeFilter(nullable: true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be included nullable:true
, otherwise database schema update will fail for existing job definitions
Hi, Has this feature been implemented ? I hace checked "Dispatch to nodes" Many thanks for your help |
@jerome83136 the message has changed, now it looks like this: |
See #1814
Add a flag to the job on create/edit for success and continue on a step without target.
This property is rendered only when
Dispatch to Nodes
is selected and is false by default.Included in export/import job via xml/yaml using
successOnEmptyNodeFilter=true
.Gui: