[JIRA] (JENKINS-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly commented on JENKINS-42000 Re: GitHub organization job losing build history Ben Fortuna yes and scm-api 2.0.4 was released before branch-api 2.0.6... just that the OSS update center can have issues presenting a consistent set of releases when the releases were made in less than 4-8h of the update center being regenerated (and also the update center does not present a self-consistent set of plugins, e.g. JENKINS-23757 is one aspect. Another aspect is that if the update center does not have e.g. scm-api 2.0.4 then it should hold back branch-api 2.0.6 until it does have it - a feature of the CloudBees update center back-end code) In any case the releases should all be available now 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-42000) GitHub organization job losing build history
Title: Message Title Ben Fortuna edited a comment on JENKINS-42000 Re: GitHub organization job losing build history Awesome, thanks so much for the quick response. I'll confirm the fix once 2.0.6 is released. [~stephenconnolly] a slight issue with installing 2.0.6 - it appears to have a dependency on scm-api 2.0.4, but the latest release is 2.0.3. 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-42000) GitHub organization job losing build history
Title: Message Title Ben Fortuna commented on JENKINS-42000 Re: GitHub organization job losing build history Awesome, thanks so much for the quick response. I'll confirm the fix once 2.0.6 is released. 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-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly commented on JENKINS-42000 Re: GitHub organization job losing build history Branch API 2.0.6 has the fix. (Well I claim it does) 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/branch/OrganizationFolder.java http://jenkins-ci.org/commit/branch-api-plugin/fef4a1490be35a31b9666006a5cec96de38d78ae Log: [FIXED JENKINS-42000] Fix the tests (and presumably the bug too) 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-42000 GitHub organization job losing build history Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/02054676abef582d137c4a2d6288d0a37586f6de Log: JENKINS-42000 Note that tests were added to track this issue Tests should have been part of original contract though 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/branch-api-plugin/9e6a295c8172d713a2459c9bb35002f4325a5df3 Log: JENKINS-42000 Pick up SCM API release and update parent 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/6570519345b9b6a78aa70818b07bfc7190f4e878 Log: JENKINS-42000 Add test case to verify issue 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/branch/OrganizationFolder.java src/test/java/integration/EventsTest.java http://jenkins-ci.org/commit/branch-api-plugin/76313ec24e6afc2fa7a7fb408a7d5753f8be5c99 Log: Merge pull request #85 from stephenc/jenkins-42000 JENKINS-42000 Communication errors in organization scanning should not delete all everything Compare: https://github.com/jenkinsci/branch-api-plugin/compare/0178b37da659...76313ec24e6a 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/49431e0b2da6268e42a33277f67db6a1ba57c136 Log: JENKINS-42000 Pick up SCM API update 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/github-branch-source-plugin/8b54a60c8ab2e980324af10dc9ed1b354f47f471 Log: JENKINS-42000 Pick up SCM API release and update parent 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java http://jenkins-ci.org/commit/github-branch-source-plugin/2531b82542540ee6e804d8afa3bff08b4bd0293e Log: Merge pull request #119 from stephenc/jenkins-42000 JENKINS-42000 Pick up SCM API update Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/85345b1c1ce0...2531b8254254 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/scm/api/SCMSourceObserver.java http://jenkins-ci.org/commit/scm-api-plugin/b4b7b6744f89965e5f33e93ecd8ad3b1b471ce9a Log: JENKINS-42000 ProjectObserver.complete should be allowed to throw IOException While technically a binary incompatibility, as all call sites except for OrganizationFolder already declare throwing IOException this should be safe 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-42000) GitHub organization job losing build history
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42000 Re: GitHub organization job losing build history Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/scm/api/SCMSourceObserver.java http://jenkins-ci.org/commit/scm-api-plugin/563db931c7be02f8056d6a4584441d6808d927d3 Log: Merge pull request #29 from stephenc/jenkins-42000 JENKINS-42000 ProjectObserver.complete should be allowed to throw IOException Compare: https://github.com/jenkinsci/scm-api-plugin/compare/101b72fd5379...563db931c7be 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-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly commented on JENKINS-42000 Re: GitHub organization job losing build history I am suspecting the root cause is: https://github.com/jenkinsci/branch-api-plugin/blob/1a964d93041d0600c03ba2dc89ce3a139ccbc487/src/main/java/jenkins/branch/OrganizationFolder.java#L1262-L1264 suppressing the exception. Here is a log from manual testing of org folders for JENKINS-36029 Started by user anonymous [Tue Feb 14 13:54:12 GMT 2017] Starting organization scan... [Tue Feb 14 13:54:12 GMT 2017] Updating actions... Looking up team details of cloudbeers... Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Team: cloudbeers [Tue Feb 14 13:54:14 GMT 2017] Consulting Bitbucket Team/Project Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Looking up repositories of team cloudbeers Proposing multibranch-demo Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Repository type: Git Looking up cloudbeers/multibranch-demo for branches Checking branch awesome from cloudbeers/multibranch-demo ‘Jenkinsfile’ found Met criteria Checking branch master from cloudbeers/multibranch-demo ‘Jenkinsfile’ found Met criteria Checking branch pinned-lib-version from cloudbeers/multibranch-demo ‘Jenkinsfile’ found Met criteria Looking up cloudbeers/multibranch-demo for pull requests Skipping pull requests for public repositories Proposing potential-train Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Repository type: Git Looking up cloudbeers/potential-train for branches Checking branch master from cloudbeers/potential-train ‘Jenkinsfile’ found Met criteria Checking branch origin-pr-branch from cloudbeers/potential-train ‘Jenkinsfile’ found Met criteria Checking branch no-jenkinsfile from cloudbeers/potential-train ‘Jenkinsfile’ not found Does not meet criteria Looking up cloudbeers/potential-train for pull requests Skipping pull requests for public repositories Proposing refactored-dollop Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Repository type: Git Looking up cloudbeers/refactored-dollop for branches Checking branch master from cloudbeers/refactored-dollop ‘Jenkinsfile’ not found Does not meet criteria Looking up cloudbeers/refactored-dollop for pull requests Skipping pull requests for public repositories Proposing glowing-rotary-phone Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Repository type: Git Looking up cloudbeers/glowing-rotary-phone for branches Checking branch master from cloudbeers/glowing-rotary-phone ‘Jenkinsfile’ not found Does not meet criteria Looking up cloudbeers/glowing-rotary-phone for pull requests Skipping pull requests for public repositories Proposing stunning-octo-tribble Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Repository type: Git Looking up cloudbeers/stunning-octo-tribble for branches Checking branch master from cloudbeers/stunning-octo-tribble ‘Jenkinsfile’ not found Does not meet criteria Looking up cloudbeers/stunning-octo-tribble for pull requests Proposing jubilant-succotash Connecting to https://bitbucket.org using stephenc/** (bitbucket.org) Repository type: Git Looking up cloudbeers/jubilant-succotash for branches Checking branch master from cloudbeers/jubilant-succotash ‘Jenkinsfile’ not found Does not meet criteria Looking up cloudbeers/jubilant-succotash for
[JIRA] (JENKINS-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-42000 GitHub organization job losing build history Change By: Stephen Connolly Assignee: Kohsuke Kawaguchi Stephen Connolly 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-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-42000 GitHub organization job losing build history Change By: Stephen Connolly Component/s: github-branch-source-plugin Component/s: github-organization-folder-plugin 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-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly commented on JENKINS-42000 Re: GitHub organization job losing build history Ben Fortuna Can you please set the system property com.cloudbees.hudson.plugins.folder.computed.BACKUP_LOG_COUNT to something high enough to catch the failure, e.g. 24h / 15min = 96 So -Dcom.cloudbees.hudson.plugins.folder.computed.FolderComputation.BACKUP_LOG_COUNT=100 Would suffice. Note, if you do not want to restart your master you can set this value by the Groocy console with the script: com.cloudbees.hudson.plugins.folder.computed.FolderComputation.BACKUP_LOG_COUNT=100 (to clear it again just remove the system property or set the value to null via the groovy console) Then wait for a failure to occur, and find the indexing/indexing.log.N which has the failure (will likely be the one with Will remove in the log text, e.g. grep "Will remove" indexing.log* but will have a Finished: SUCCESS. OTOH if you have an orphaned item strategy that is retaining them for a period of time it may be harder to find the one with the suppressed (but hopefully logged) stack trace. ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42000) GitHub organization job losing build history
Title: Message Title Stephen Connolly commented on JENKINS-42000 Re: GitHub organization job losing build history Can you provide the plugin versions? 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-42000) GitHub organization job losing build history
Title: Message Title Ben Fortuna created an issue Jenkins / JENKINS-42000 GitHub organization job losing build history Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2017/Feb/14 12:25 AM Priority: Critical Reporter: Ben Fortuna We have a large GitHub organization folder job (over 100 repos) that is scanned every 15 mins for changes. Occasionally (usually overnight I think) branches are losing the build history and are reset to build number 1. I suspect the branch indexing is somehow losing communication with GitHub and the branch is deleted and then recreated on the next successful scan. Note this doesn't appear to happen in business hours, so possibly is a result of overnight resource conservation (Jenkins is not currently shutdown overnight). As a workaround I have configured to not delete branches unless unchanged for 7 days, however some branches are not updated this frequently, and I don't want to extend this period as we'll have too many jobs hanging around. Note also that we don't currently use webhooks to detect changes, which is why it is a periodic scan every 15 mins. Add Comment