[JIRA] (JENKINS-56935) Multibranch pipeline orphaned item strategy can't be set to 0

[thefriendlycoder@gmail.com (JIRA)]

Kevin Phillips created an issue

Jenkins / JENKINS-56935 Multibranch pipeline orphaned item strategy can't be set to 0 Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-04-08 13:57 Priority: Minor Reporter: Kevin Phillips Currently the orphaned item strategy for a multibranch pipeline job does not allow one to set retention policy for 0 days / 0 branches. The form validator says "Not a positive integer". I would recommend changing this form validation to accept 0 as a valid "positive" integer to allow immediate deletion of branches from a multibranch pipeline job as soon as the respective branch is deleted in source control. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[carlosjuangp@gmail.com (JIRA)]

Carlos Juan Gómez Peñalver commented on JENKINS-56935

Re: Multibranch pipeline orphaned item strategy can't be set to 0 Kevin Phillips Looks like the solution is to leave both fields empty  https://stackoverflow.com/questions/51734259/jenkins-multibranch-pipeline-wont-prune-deleted-branches Maybe 0 should be equivalent. Groovy DSL documentation for these fields says that the default value is "-1" https://jenkinsci.github.io/job-dsl-plugin/#path/javaposse.jobdsl.dsl.jobs.OrganizationFolderJob.orphanedItemStrategy-discardOldItems

Add Comment

[thefriendlycoder@gmail.com (JIRA)]

Kevin Phillips commented on JENKINS-56935

Re: Multibranch pipeline orphaned item strategy can't be set to 0

Confirmed. Sometimes the obvious solution is the correct one. Thanks for pointing this out.

Add Comment

[thefriendlycoder@gmail.com (JIRA)]

Kevin Phillips resolved as Fixed

Jenkins / JENKINS-56935

Multibranch pipeline orphaned item strategy can't be set to 0

Change By: Kevin Phillips Status: Open Resolved Resolution: Fixed

Add Comment