Jenkins cannot access git











up vote
1
down vote

favorite












After a crash of the Jenkins server, I cannot start my projects builds.



I get this weird message. Any clues?



hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/master:refs/remotes/origin/master --prune" returned status code 128:
stdout:
stderr: error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
fatal: loose object 10f103eb6e4590be766e67ca961e65f5c4e6836c (stored in .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c) is corrupt
fatal: The remote end hung up unexpectedly









share|improve this question




























    up vote
    1
    down vote

    favorite












    After a crash of the Jenkins server, I cannot start my projects builds.



    I get this weird message. Any clues?



    hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/master:refs/remotes/origin/master --prune" returned status code 128:
    stdout:
    stderr: error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
    error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
    fatal: loose object 10f103eb6e4590be766e67ca961e65f5c4e6836c (stored in .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c) is corrupt
    fatal: The remote end hung up unexpectedly









    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      After a crash of the Jenkins server, I cannot start my projects builds.



      I get this weird message. Any clues?



      hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/master:refs/remotes/origin/master --prune" returned status code 128:
      stdout:
      stderr: error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
      error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
      fatal: loose object 10f103eb6e4590be766e67ca961e65f5c4e6836c (stored in .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c) is corrupt
      fatal: The remote end hung up unexpectedly









      share|improve this question















      After a crash of the Jenkins server, I cannot start my projects builds.



      I get this weird message. Any clues?



      hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/master:refs/remotes/origin/master --prune" returned status code 128:
      stdout:
      stderr: error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
      error: object file .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c is empty
      fatal: loose object 10f103eb6e4590be766e67ca961e65f5c4e6836c (stored in .git/objects/10/f103eb6e4590be766e67ca961e65f5c4e6836c) is corrupt
      fatal: The remote end hung up unexpectedly






      git jenkins






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 8 at 14:52









      Mukesh M

      1,13561627




      1,13561627










      asked Nov 8 at 11:03









      Jandroid1

      415




      415
























          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          In my case I did following



          Select Workspace and click on Wipe Out Current Workspace. This will delete your workspace.



          Now just start new build and it will work.



          Jenkins  Wipe Out Current Workspace






          share|improve this answer






























            up vote
            0
            down vote













            Had the same a few times.



            Sometimes the above answer may of @"Mukesh M" may help - that is a decent approach. In other cases, the following approach helped me a few times.



            First visit the /var/jenkins_home/caches folder. Delete the git-hashes. The next start of the job will retrieve everything from git again so the job will run smooth again. So omitting the git cache.






            share|improve this answer





















              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














               

              draft saved


              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206429%2fjenkins-cannot-access-git%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              0
              down vote













              In my case I did following



              Select Workspace and click on Wipe Out Current Workspace. This will delete your workspace.



              Now just start new build and it will work.



              Jenkins  Wipe Out Current Workspace






              share|improve this answer



























                up vote
                0
                down vote













                In my case I did following



                Select Workspace and click on Wipe Out Current Workspace. This will delete your workspace.



                Now just start new build and it will work.



                Jenkins  Wipe Out Current Workspace






                share|improve this answer

























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  In my case I did following



                  Select Workspace and click on Wipe Out Current Workspace. This will delete your workspace.



                  Now just start new build and it will work.



                  Jenkins  Wipe Out Current Workspace






                  share|improve this answer














                  In my case I did following



                  Select Workspace and click on Wipe Out Current Workspace. This will delete your workspace.



                  Now just start new build and it will work.



                  Jenkins  Wipe Out Current Workspace







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 8 at 13:08

























                  answered Nov 8 at 13:03









                  Mukesh M

                  1,13561627




                  1,13561627
























                      up vote
                      0
                      down vote













                      Had the same a few times.



                      Sometimes the above answer may of @"Mukesh M" may help - that is a decent approach. In other cases, the following approach helped me a few times.



                      First visit the /var/jenkins_home/caches folder. Delete the git-hashes. The next start of the job will retrieve everything from git again so the job will run smooth again. So omitting the git cache.






                      share|improve this answer

























                        up vote
                        0
                        down vote













                        Had the same a few times.



                        Sometimes the above answer may of @"Mukesh M" may help - that is a decent approach. In other cases, the following approach helped me a few times.



                        First visit the /var/jenkins_home/caches folder. Delete the git-hashes. The next start of the job will retrieve everything from git again so the job will run smooth again. So omitting the git cache.






                        share|improve this answer























                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          Had the same a few times.



                          Sometimes the above answer may of @"Mukesh M" may help - that is a decent approach. In other cases, the following approach helped me a few times.



                          First visit the /var/jenkins_home/caches folder. Delete the git-hashes. The next start of the job will retrieve everything from git again so the job will run smooth again. So omitting the git cache.






                          share|improve this answer












                          Had the same a few times.



                          Sometimes the above answer may of @"Mukesh M" may help - that is a decent approach. In other cases, the following approach helped me a few times.



                          First visit the /var/jenkins_home/caches folder. Delete the git-hashes. The next start of the job will retrieve everything from git again so the job will run smooth again. So omitting the git cache.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 10 at 8:58









                          tjm1706

                          2,59932156




                          2,59932156






























                               

                              draft saved


                              draft discarded



















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206429%2fjenkins-cannot-access-git%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Schultheiß

                              Liste der Kulturdenkmale in Wilsdruff

                              Android Play Services Check