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

Flag for success when node filter does not match any node #2456

Merged
merged 7 commits into from
Jun 20, 2017

Conversation

jtobard
Copy link
Contributor

@jtobard jtobard commented Apr 21, 2017

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:
01_job_edit

@@ -67,6 +68,7 @@ public class BaseNodeFilters {
nodeIncludeOsVersion(nullable: true)
nodeExcludeOsVersion(nullable: true)
nodeExcludePrecedence(nullable: true)
//successOnEmptyNodeFilter(nullable: true)
Copy link
Member

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

@gschueler gschueler modified the milestone: 2.9.0 May 4, 2017
@gschueler gschueler changed the base branch from master to prerelease-2.9.0 June 20, 2017 21:11
@gschueler gschueler merged commit 357f5bf into rundeck:prerelease-2.9.0 Jun 20, 2017
@jerome83136
Copy link

Hi,
I just installed the lastest version and I can't find "Success on a step without targed node ?" on the GUI

Has this feature been implemented ?

I hace checked "Dispatch to nodes"

Many thanks for your help
Best regards
Jérôme

@jtobard
Copy link
Contributor Author

jtobard commented Mar 27, 2018

@jerome83136 the message has changed, now it looks like this:
imagen

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

Successfully merging this pull request may close these issues.

3 participants