[JIRA] (JENKINS-40058) Jobs not removed when branch gets removed in case of orphaned item strategy set
Title: Message Title Sid S commented on JENKINS-40058 Re: Jobs not removed when branch gets removed in case of orphaned item strategy set I'm also seeing that orphaned items aren't removed when specified via the jenkin's UI (a multi branch project => configure => Orphaned Item Strategy). If this works only via the Jenkinsfile, it ought to be removed from the UI to avoid confusion. A transition could be to put Stephen's comment in the UI before removing it completely. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40058) Jobs not removed when branch gets removed in case of orphaned item strategy set
Title: Message Title Stephen Connolly resolved as Not A Defect The strategy for removal of builds is controlled by the Jenkinsfile, e.g. something like properties([buildDiscarder(logRotator(artifactNumToKeepStr: '5', numToKeepStr: env.BRANCH_NAME=='master'?'10':'5'))]) which will keep the last 10 builds of master and the last 5 builds of all other branches (but obviously each branch could instead have its own value hard-coded as long as you are careful with merge conflicts between branches Jenkins / JENKINS-40058 Jobs not removed when branch gets removed in case of orphaned item strategy set Change By: Stephen Connolly Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40058) Jobs not removed when branch gets removed in case of orphaned item strategy set
Title: Message Title Sergey Zhemzhitsky created an issue Jenkins / JENKINS-40058 Jobs not removed when branch gets removed in case of orphaned item strategy set Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Nov/27 9:59 PM Environment: Jenkins 2.33 Ubuntu 14.04 LTS Priority: Major Reporter: Sergey Zhemzhitsky If there is "Orphaned Item Strategy" configured with the non-zero "Max # of old items to keep" the jobs for removed branches are not removed. When branch indexing occurs I have the following log for the removed branch ... Looking up / for pull requests Evaluating orphaned items in » build-multi Will not remove DMC-1234-test as it is only #1 in the list ... It would be great to have an option (which is "on" by default) whether it is necessary to remove builds for deleted branches or not. I suppose it's more expected behavior that the job for the removed branch will be deleted than will be kept until an expected number of builds occurs (that may never happen as the branch is already deleted) I have the orphan strategy setup like the following ... with Max # of old items to keep set to an empty string. Then while reindexing Jenkins says ... Looking up / for pull requests Evaluating orphaned items in » build-multi Will not remove D
