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

org.eclipse.jgit.errors.MissingObjectException: Missing commit

    Details

    • Similar Issues:
    • Sprint:
      tasman, Blue Ocean 1.3

      Description

      Upgrading the git-client plugin and noticed that pull request builds behind our GitHub Organization Folders started to fail across the board with the following exception:

      Caught: hudson.plugins.git.GitException: org.eclipse.jgit.errors.MissingObjectException: Missing commit 06f18bc86352142786ef533c91350863b382631c
      

      Full log from one such build.

      Branch indexing
      Connecting to https://api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin)
      Cloning the remote Git repository
      remote: Counting objects
      remote: Compressing objects
      Receiving objects
      Resolving deltas
      Updating references
      Merging master commit 3d19d905686b173b8916ee0247d906f536429621 into PR head commit 06f18bc86352142786ef533c91350863b382631c
      Merge succeeded, producing 06f18bc86352142786ef533c91350863b382631c
      Checking out Revision 06f18bc86352142786ef533c91350863b382631c (PR-458)
      First time build. Skipping changelog.
      [Pipeline] properties
      [Pipeline] node
      Running on celery in /home/jenkins/agent-workspace/workspace/Infra_jenkins.io_PR-458-WGT3J3NBHKU6J2KK5XLMWWKKN2CDZN42K6EQVSUQWUMNA4CYPZQA
      [Pipeline] {
      [Pipeline] stage (Clean workspace)
      Using the ‘stage’ step without a block argument is deprecated
      Entering stage Clean workspace
      Proceeding
      [Pipeline] deleteDir
      [Pipeline] sh
      [Infra_jenkins.io_PR-458-WGT3J3NBHKU6J2KK5XLMWWKKN2CDZN42K6EQVSUQWUMNA4CYPZQA] Running shell script
      + ls -lah
      total 24K
      drwxrwxr-x  2 jenkins jenkins 4.0K Nov 17 14:37 .
      drwxrwxr-x 94 jenkins jenkins  20K Nov 17 14:37 ..
      [Pipeline] stage (Checkout source)
      Using the ‘stage’ step without a block argument is deprecated
      Entering stage Checkout source
      Proceeding
      [Pipeline] checkout
      Cloning the remote Git repository
      remote: Counting objects
      remote: Compressing objects
      Receiving objects
      Resolving deltas
      Updating references
      Merging master commit 3d19d905686b173b8916ee0247d906f536429621 into PR head commit 06f18bc86352142786ef533c91350863b382631c
      Merge succeeded, producing 06f18bc86352142786ef533c91350863b382631c
      Checking out Revision 06f18bc86352142786ef533c91350863b382631c (PR-458)
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] echo
      Caught: hudson.plugins.git.GitException: org.eclipse.jgit.errors.MissingObjectException: Missing commit 06f18bc86352142786ef533c91350863b382631c
      [Pipeline] mail
      [Pipeline] End of Pipeline
      

        Attachments

          Issue Links

            Activity

            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Mark Waite
            Path:
            pom.xml
            http://jenkins-ci.org/commit/git-client-plugin/c90b3f32be6bb6921be634fbaee6ef74084e3bdb
            Log:
            Revert "Use jgit 4.5.3"

            JENKINS-39832 may be visible again due to the update to JGit 4.5.3.
            This revert is a test which will be used in the staging environment
            to confirm (or refute) that the change from JGit 4.5.2 to JGit 4.5.3
            introduces "missing object exception" reports.

            This reverts commit 4de8bb5a5e77e94e422828798d0bbb218a7840cc.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: pom.xml http://jenkins-ci.org/commit/git-client-plugin/c90b3f32be6bb6921be634fbaee6ef74084e3bdb Log: Revert "Use jgit 4.5.3" JENKINS-39832 may be visible again due to the update to JGit 4.5.3. This revert is a test which will be used in the staging environment to confirm (or refute) that the change from JGit 4.5.2 to JGit 4.5.3 introduces "missing object exception" reports. This reverts commit 4de8bb5a5e77e94e422828798d0bbb218a7840cc.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Mark Waite
            Path:
            pom.xml
            http://jenkins-ci.org/commit/git-client-plugin/7fa60c6625590522ada79fac614d2101e28ef735
            Log:
            Merge pull request #266 from MarkEWaite/revert-jgit-4.5.3

            Revert "Use jgit 4.5.3" - test JENKINS-39832

            Compare: https://github.com/jenkinsci/git-client-plugin/compare/7e62650ab7a6...7fa60c662559

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: pom.xml http://jenkins-ci.org/commit/git-client-plugin/7fa60c6625590522ada79fac614d2101e28ef735 Log: Merge pull request #266 from MarkEWaite/revert-jgit-4.5.3 Revert "Use jgit 4.5.3" - test JENKINS-39832 Compare: https://github.com/jenkinsci/git-client-plugin/compare/7e62650ab7a6...7fa60c662559
            Hide
            markewaite Mark Waite added a comment -

            The previously mentioned revert is unlikely to help this case.

            The Blue Ocean autofavorite plugin (FavoritingScmListener.getChangeSet) is asking the workspace for the changeset for the tip of the pipeline shared library.  It should be asking the workspace for the changeset for the tip of the workspace.

            In my case, I see that the autofavorite code is asking for 88016e...  That SHA1 is the tip of the master branch of my pipeline shared library, but is does not exist in the workspace of the pipeline for the "docker" or "git-client-plugin" or "hello-world-plugin" where I saw the problem.

            As far as I can tell, this is a problem specific to the Blue Ocean autofavorite plugin and its interaction with pipeline shared libraries.  If the pipeline job is not executing in a context which provides a pipeline shared library, then this failure should not be visible.

            Show
            markewaite Mark Waite added a comment - The previously mentioned revert is unlikely to help this case. The Blue Ocean autofavorite plugin ( FavoritingScmListener.getChangeSet ) is asking the workspace for the changeset for the tip of the pipeline shared library .  It should be asking the workspace for the changeset for the tip of the workspace . In my case, I see that the autofavorite code is asking for 88016e...  That SHA1 is the tip of the master branch of my pipeline shared library, but is does not exist in the workspace of the pipeline for the "docker" or "git-client-plugin" or "hello-world-plugin" where I saw the problem. As far as I can tell, this is a problem specific to the Blue Ocean autofavorite plugin and its interaction with pipeline shared libraries.  If the pipeline job is not executing in a context which provides a pipeline shared library, then this failure should not be visible.
            Hide
            rtyler R. Tyler Croy added a comment -

            Wow Mark Waite, thanks for digging into this, I'm glad you found what appears to be the root cause of the issue.

            Show
            rtyler R. Tyler Croy added a comment - Wow Mark Waite , thanks for digging into this, I'm glad you found what appears to be the root cause of the issue.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Mark Waite
            Path:
            pom.xml
            http://jenkins-ci.org/commit/git-client-plugin/5119057d51db7e9859d0c4fd51fcb0f59358c288
            Log:
            Use jgit 4.5.3

            Testing for JENKINS-39832 showed that the JGit change was unrelated to
            the missing object exception.

            This reverts commit c90b3f32be6bb6921be634fbaee6ef74084e3bdb.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: pom.xml http://jenkins-ci.org/commit/git-client-plugin/5119057d51db7e9859d0c4fd51fcb0f59358c288 Log: Use jgit 4.5.3 Testing for JENKINS-39832 showed that the JGit change was unrelated to the missing object exception. This reverts commit c90b3f32be6bb6921be634fbaee6ef74084e3bdb.

              People

              • Assignee:
                Unassigned
                Reporter:
                rtyler R. Tyler Croy
              • Votes:
                2 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: