[JIRA] (JENKINS-54578) Cannot delete last category

2018-11-18 Thread aeo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Agulló commented on  JENKINS-54578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot delete last category   
 

  
 
 
 
 

 
 Ready to review on GitHub.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-54578) Cannot delete last category

2018-11-18 Thread aeo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Agulló updated  JENKINS-54578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54578  
 
 
  Cannot delete last category   
 

  
 
 
 
 

 
Change By: 
 Diego Agulló  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-54578) Cannot delete last category

2018-11-17 Thread aeo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Agulló assigned an issue to Diego Agulló  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54578  
 
 
  Cannot delete last category   
 

  
 
 
 
 

 
Change By: 
 Diego Agulló  
 
 
Assignee: 
 Diego Agulló  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-54578) Cannot delete last category

2018-11-17 Thread aeo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Agulló started work on  JENKINS-54578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Diego Agulló  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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-54630) Scan Organization Folder fails when a repository is deleted but configured to redirect

2018-11-17 Thread aeo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Agulló updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54630  
 
 
  Scan Organization Folder fails when a repository is deleted but configured to redirect
 

  
 
 
 
 

 
Change By: 
 Diego Agulló  
 

  
 
 
 
 

 
 I have a reporsitory in my Bitbucket account that was deleted but it's configured to redirect to an other URL, hence not 100% deleted and can still be accessed through [https://bitbucket.org/geniousphp/soam]When I run my scan, it fails because of that and throw the error{code:java}ERROR: [Wed Nov 14 14:59:11 UTC 2018] Could not fetch sources from navigator com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator@2e752b5f java.io.FileNotFoundException: URL:https://api.bitbucket.org/2.0/repositories/geniousphp/soamat com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequestAsInputStream(BitbucketCloudApiClient.java:765) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:785) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:330) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.getRepositoryType(BitbucketSCMSource.java:504) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:548) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:374) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:328) at jenkins.branch.MultiBranchProjectFactory$BySCMSourceCriteria.recognizes(MultiBranchProjectFactory.java:263) at jenkins.branch.OrganizationFolder$SCMSourceObserverImpl$1.recognizes(OrganizationFolder.java:1346) at jenkins.branch.OrganizationFolder$SCMSourceObserverImpl$1.complete(OrganizationFolder.java:1361) at jenkins.scm.api.trait.SCMNavigatorRequest.process(SCMNavigatorRequest.java:256) at jenkins.scm.api.trait.SCMNavigatorRequest.process(SCMNavigatorRequest.java:206) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:487) at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:458) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.OrganizationFolder$OrganizationScan.run(OrganizationFolder.java:910) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429){code} I think that this issue can be similar to  Jenkins JENKINS -47900The thing is that I can't workaround this and hence it's definitely a blocker. I would love to delete completely that repo but it's not possible from Bitbucket UI, not API. The only way to remove it is by contacting Bitbucket ([https://confluence.atlassian.com/bitbucket/how-do-i-remove-a-redirect-url-i-supplied-when-i-deleted-my-repo-282173855.html)|https://confluence.atlassian.com/bitbucket/how-do-i-remove-a-redirect-url-i-supplied-when-i-deleted-my-repo-282173855.html]  
  

[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder

2018-11-13 Thread aeo...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Agulló commented on  JENKINS-54108  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "JIRA: Progress issues by workflow action" fails when job is located within a folder   
 

  
 
 
 
 

 
 I haven't been able to reproduce this issue using the versions listed on the issue description. I tested this on the .war version on a fresh install (with a fresh Jira as well). Jason Weiss Anna Tyshkevich do you have any other detail about your setup to try and triage this issue?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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