Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55388

multibranch pipeline deleting history and building unexpectedly

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Environment:
    • Similar Issues:

      Description

      I have a multibranch pipeline setup with a Jenkinsfile. I have a release branch (current-release) that isn't updated very often. Every once in a while, around a month or so, Jenkins decides to delete all of the previous builds of the branch and build the branch again. The build number starts at 1 again.

      I checked my repository scan log and it had already turned over since the build, so I don't know what was in there. The most recent build said it started because of branch indexing.

      I have "Discard old items" set to 1 days. My understanding this is just for deleting old branches.

      I'm using a github repository as my source with push notifications turned on.

      In my jenkins stdout/stderr log I see the following. The build occurred at 12:51pm. Could this cleanup possibly have deleted information for the wrong branch?

      INFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?
      Jan 02, 2019 12:33:29 PM jenkins.branch.WorkspaceLocatorImpl getWorkspaceRoot
      WARNING: JENKINS-2111 path sanitization ineffective when using legacy Workspace Root Directory ?${ITEM_ROOTDIR}/workspace?; switch to ?${JENKINS_HOME}/workspace/${ITEM_FULL_NAME}? as in JENKINS-8446 / JENKINS-21942
      Jan 02, 2019 12:33:32 PM jenkins.branch.WorkspaceLocatorImpl getWorkspaceRoot
      WARNING: JENKINS-2111 path sanitization ineffective when using legacy Workspace Root Directory ?${ITEM_ROOTDIR}/workspace?; switch to ?${JENKINS_HOME}/workspace/${ITEM_FULL_NAME}? as in JENKINS-8446 / JENKINS-21942
      Jan 02, 2019 12:33:32 PM jenkins.branch.WorkspaceLocatorImpl$Deleter$CleanupTask run
      INFO: deleting obsolete workspace C:\Users\fll\jenkins\workspace\SW_issue_675_group-name-location on fll-build
      Jan 02, 2019 12:33:32 PM jenkins.branch.MultiBranchProject$BranchIndexing run
      INFO: FLL-SW #20190102.123300 branch indexing action completed: SUCCESS in 32 sec
      Jan 02, 2019 12:34:09 PM jenkins.branch.WorkspaceLocatorImpl$Deleter$CleanupTask run
      INFO: deleting obsolete workspace C:\Users\fll\jenkins\workspace\SW_issue_675_group-name-location@tmp on fll-build
      Jan 02, 2019 12:51:02 PM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol
      

      The question is why is my build history getting deleted?

       

        Attachments

          Activity

          Hide
          suganyaravikumar Suganya Ravikumar added a comment -

          Is this related to JENKINS-54126?

          Show
          suganyaravikumar Suganya Ravikumar added a comment - Is this related to  JENKINS-54126 ?
          Hide
          rompic Roman Pickl added a comment -

          I see this (or something related) for all branches. once in a while jenkins throws away everything (maybe after a problem with scanning our local github) and restarts all builds.

          Show
          rompic Roman Pickl added a comment - I see this (or something related) for all branches. once in a while jenkins throws away everything (maybe after a problem with scanning our local github) and restarts all builds.
          Hide
          morganr87 Morgan Robertson added a comment -
          Show
          morganr87 Morgan Robertson added a comment - This seems very similar to  https://issues.jenkins-ci.org/browse/JENKINS-55220
          Hide
          morganr87 Morgan Robertson added a comment -

          Do we all have the 'Discard old items' item enabled in Jenkins?  I have a suspicion that what's happening is that GitHub or Bitbucket or whatever git service we use occasionally fails to properly respond to the Jenkins poll request and then Jenkins removes the branch due to the 'Discard old items' option.  I'm going to try disabling this.

          If so, two potential fixes:

          • Allow certain branches to be excepted from the 'Discard old items' job.
          • Make every Bitbucket / GitHub / etc. reliably respond to requests (hah).
          Show
          morganr87 Morgan Robertson added a comment - Do we all have the 'Discard old items' item enabled in Jenkins?  I have a suspicion that what's happening is that GitHub or Bitbucket or whatever git service we use occasionally fails to properly respond to the Jenkins poll request and then Jenkins removes the branch due to the 'Discard old items' option.  I'm going to try disabling this. If so, two potential fixes: Allow certain branches to be excepted from the 'Discard old items' job. Make every Bitbucket / GitHub / etc. reliably respond to requests (hah).
          Hide
          jlanderson Jesse Anderson added a comment -

          For us, this was happening because the branch was also picked up as a pull request and was found in the pull request tab. The message in the logs read `Will remove xxx as it is too old`, but when we closed the PR and rescanned, it remained in the branches tab. Not sure why the log messages were so unrelated to the actual issue. 

          Show
          jlanderson Jesse Anderson added a comment - For us, this was happening because the branch was also picked up as a pull request and was found in the pull request tab. The message in the logs read `Will remove xxx as it is too old`, but when we closed the PR and rescanned, it remained in the branches tab. Not sure why the log messages were so unrelated to the actual issue. 

            People

            • Assignee:
              Unassigned
              Reporter:
              jpschewe jpschewe
            • Votes:
              19 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated: