[JIRA] (JENKINS-38348) When the Github API is not responding, all jobs in the Org folder disappear.

2016-11-11 Thread e...@borgstrom.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Borgstrom edited a comment on  JENKINS-38348  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When the Github API is not responding, all jobs in the Org folder disappear.   
 

  
 
 
 
 

 
 This also occurs if you hit the rate limit while scanning:{noformat}Nov 10, 2016 2:30:35 PM INFO jenkins.branch.WorkspaceLocatorImpl$Deleter cleanUpdeleting obsolete workspace /var/lib/jenkins/workspace/... Nov 10, 2016 2:30:35 PM WARNING org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl maybeApplyFailed to apply GitHub Org Folder theme to GitHub/...org.jenkinsci.plugins.github_branch_source.RateLimitExceededException: GitHub API rate limit exceeded{noformat}I agree that this is a rather serious problem and that these errors should  *not*  make the jobs disappear.  It was very unexpected to lose all of our build history.  We use the Artifactory plugin and remove artifacts as we clean up builds, so this means that we will end up leaving some builds orphaned in Artifactory and lose out on being able to trace artifacts back to builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38348) When the Github API is not responding, all jobs in the Org folder disappear.

2016-11-11 Thread e...@borgstrom.ca (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Borgstrom commented on  JENKINS-38348  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When the Github API is not responding, all jobs in the Org folder disappear.   
 

  
 
 
 
 

 
 This also occurs if you hit the rate limit while scanning: 

 
Nov 10, 2016 2:30:35 PM INFO jenkins.branch.WorkspaceLocatorImpl$Deleter cleanUp
deleting obsolete workspace /var/lib/jenkins/workspace/... 

Nov 10, 2016 2:30:35 PM WARNING org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl maybeApply
Failed to apply GitHub Org Folder theme to GitHub/...
org.jenkinsci.plugins.github_branch_source.RateLimitExceededException: GitHub API rate limit exceeded
 

 I agree that this is a rather serious problem and that these errors should make the jobs disappear. It was very unexpected to lose all of our build history. We use the Artifactory plugin and remove artifacts as we clean up builds, so this means that we will end up leaving some builds orphaned in Artifactory and lose out on being able to trace artifacts back to builds.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38348) When the Github API is not responding, all jobs in the Org folder disappear.

2016-09-19 Thread car...@barrobes.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carles Barrobés updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38348  
 
 
  When the Github API is not responding, all jobs in the Org folder disappear.   
 

  
 
 
 
 

 
Change By: 
 Carles Barrobés  
 

  
 
 
 
 

 
 h2. Current behaviourNormally we should see our repositories and builds in the organization folder, but they are empty: !image-2016-09-19-17-57-30-814.png|thumbnail! Looking at the logs, it looks like there were issues accessing the Github API today: !image-2016-09-19-17-59-31-216.png|thumbnail! h2. Expected behaviourMy expectation would be that upon connectivity errors to Github, nothing is deleted , and we can still browse previous builds etc . Else we can't even access  valid builds etc  reports from active PRs that were built before connectivity issues started .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-38348) When the Github API is not responding, all jobs in the Org folder disappear.

2016-09-19 Thread car...@barrobes.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carles Barrobés created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38348  
 
 
  When the Github API is not responding, all jobs in the Org folder disappear.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Attachments: 
 image-2016-09-19-17-57-30-814.png, image-2016-09-19-17-59-31-216.png  
 
 
Components: 
 github-organization-folder-plugin  
 
 
Created: 
 2016/Sep/19 4:01 PM  
 
 
Environment: 
 Jenkins 2.7.4  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Carles Barrobés  
 

  
 
 
 
 

 
 Current behaviour Normally we should see our repositories and builds in the organization folder, but they are empty:Looking at the logs, it looks like there were issues accessing the Github API today:Expected behaviour My expectation would be that upon connectivity errors to Github, nothing is deleted. Else we can't even access valid builds etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment