[JIRA] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request

2016-06-09 Thread sorin.sbar...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sorin Sbarnea reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Sorry but this bug was closed without giving an explanation for the reported problem.  Currently, the list of sub-projects (branches) is growing indefinitely and we were not able to find any option for removal of the old ones. 
Git flow does state that branches are supposed to be removed after they are merged and we are doing this but it seems that Jenkins never removes them and now we have hundreds of them for each repository. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35251 
 
 
 
  Provide different strategies for repositories and branches / pull request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sorin Sbarnea 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 

[JIRA] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request

2016-06-07 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Recena Soto commented on  JENKINS-35251 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provide different strategies for repositories and branches / pull request  
 
 
 
 
 
 
 
 
 
 
Jesse Glick What is the alternative? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request

2016-06-02 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
As designed. Children of computed folders are intentionally read-only. If you want them to go away after some time, you use an orphaned item strategy. If you want them to go away immediately, delete the repository (or at least its Jenkinsfile on all open branches). 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35251 
 
 
 
  Provide different strategies for repositories and branches / pull request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi Jesse Glick 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups 

[JIRA] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request

2016-05-31 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35251 
 
 
 
  Provide different strategies for repositories and branches / pull request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Allan BURDAJEWICZ 
 
 
 
 
 
 
 
 
 
 Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/ branchs branches /pr are never discarded.Discussed solutions would be to either:*  Add the option to Delete items regardless of the Discard Policy*  Adapt/re-think the Orphaned Item Strategy*  Add the option to Delete items*  Provide another Strategy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request

2016-05-31 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35251 
 
 
 
  Provide different strategies for repositories and branches / pull request  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 github-organization-folder-plugin 
 
 
 

Created:
 

 2016/Jun/01 1:19 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Allan BURDAJEWICZ 
 
 
 
 
 
 
 
 
 
 
Using GitHub Organization Folder, if I disable the option "Discard old items" or Enable it to keep old items for 1000 days, jobs associated to removed repositories/branchs/pr are never discarded. 
Discussed solutions would be to either: 
 

Adapt/re-think the Orphaned Item Strategy
 

Add the option to Delete items
 

Provide another Strategy