• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • git-plugin
    • jenkins 1.583, git plugin 2.2.6, git client plugin 1.10.2. All current versions

      When I attempt to connect to a git repo, the Git plugin returns this error below the Repository URL field:

      javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64
      at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:783)
      at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
      at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
      at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
      at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
      at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
      at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
      at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
      at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
      at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
      at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636)
      at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
      at ....

      and so on

          [JENKINS-25013] Git Plugin No Class Def Found Error

          David Ammons added a comment -

          also, i'm talking to a gitblit repo

          David Ammons added a comment - also, i'm talking to a gitblit repo

          Mark Waite added a comment -

          Does the same failure happen if you use the following URLs?

          Mark Waite added a comment - Does the same failure happen if you use the following URLs? git://github.com/jenkinsci/git-client-plugin.git https://github.com/jenkinsci/git-client-plugin.git

          Mark Waite added a comment -

          Unfortunately, I can't duplicate the problem. The steps I took to try to duplicate the problem included:

          1. Download jenkins.war 1.583
          2. Run it from a freshly created temporary directory (JENKINS_HOME=$PWD java -jar jenkins.war)
          3. Update all the plugins to the latest versions and restart
          4. Install git plugin and restart
          5. Create a new freestyle project named "gitblit"
          6. Configure Git as the SCM for the freestyle project, with git://github.com/jenkinsci/git-client-plugin.git as the repo URL
          7. Choose gitblit as the repository browser and enter https://github.com/jenkinsgit/git-client-plugin.git

          I was running on a Ubuntu Linux 14.04 using Oracle JDK 1.7.0_67 Can you compare my steps to the steps you took in case there are relevant differences between your environment and mine?

          Mark Waite added a comment - Unfortunately, I can't duplicate the problem. The steps I took to try to duplicate the problem included: Download jenkins.war 1.583 Run it from a freshly created temporary directory (JENKINS_HOME=$PWD java -jar jenkins.war) Update all the plugins to the latest versions and restart Install git plugin and restart Create a new freestyle project named "gitblit" Configure Git as the SCM for the freestyle project, with git://github.com/jenkinsci/git-client-plugin.git as the repo URL Choose gitblit as the repository browser and enter https://github.com/jenkinsgit/git-client-plugin.git I was running on a Ubuntu Linux 14.04 using Oracle JDK 1.7.0_67 Can you compare my steps to the steps you took in case there are relevant differences between your environment and mine?

          David Ammons added a comment -

          Per your suggestion, I tested by changing the repo to https://github.com/jenkinsci/git-client-plugin.git, and it doesn't trigger the error, so the issue must have something to do with communication with gitblit?

          David Ammons added a comment - Per your suggestion, I tested by changing the repo to https://github.com/jenkinsci/git-client-plugin.git , and it doesn't trigger the error, so the issue must have something to do with communication with gitblit?

          David Ammons added a comment -

          It might help to note that I'm running several webapps in tomcat side by side: a home grown app, gitblit, jenkins, and solr.

          David Ammons added a comment - It might help to note that I'm running several webapps in tomcat side by side: a home grown app, gitblit, jenkins, and solr.

          Mark Waite added a comment - - edited

          Could you also try running the test with your gitblit repository, but using jenkins.war with its self-contained HTTP server, rather than tomcat? I'd like to confirm that it is not related to your use of tomcat.

          JENKINS_HOME=/tmp/JENKINS-25013
          export JENKINS_HOME
          mkdir $JENKINS_HOME
          java -jar /usr/share/jenkins/jenkins.war --httpPort=10101

          Once that is started, install the git plugin in the Jenkins at http://localhost:10101/, define a job and confirm that it behaves the same as your tomcat configured Jenkins. I expect it will, and that will give further credence to the issue being somehow related to the gitblit browser code in the git plugin, rather than being related to your tomcat configuration.

          Mark Waite added a comment - - edited Could you also try running the test with your gitblit repository, but using jenkins.war with its self-contained HTTP server, rather than tomcat? I'd like to confirm that it is not related to your use of tomcat. JENKINS_HOME=/tmp/ JENKINS-25013 export JENKINS_HOME mkdir $JENKINS_HOME java -jar /usr/share/jenkins/jenkins.war --httpPort=10101 Once that is started, install the git plugin in the Jenkins at http://localhost:10101/ , define a job and confirm that it behaves the same as your tomcat configured Jenkins. I expect it will, and that will give further credence to the issue being somehow related to the gitblit browser code in the git plugin, rather than being related to your tomcat configuration.

          David Ammons added a comment -

          I'll give it a try later. In the meantime, the only thing I could do to fix it was to copy the commons-codec 1.8 jar from the jenkins war into tomcat's lib dir.

          David Ammons added a comment - I'll give it a try later. In the meantime, the only thing I could do to fix it was to copy the commons-codec 1.8 jar from the jenkins war into tomcat's lib dir.

          Mark Waite added a comment -

          I can't explain why Base64 would be needed by either the git plugin or the git client plugin, since neither of them have any reference to the Base64 class.

          Mark Waite added a comment - I can't explain why Base64 would be needed by either the git plugin or the git client plugin, since neither of them have any reference to the Base64 class.

          Daniel Beck added a comment -

          Full stack trace may be helpful if there are nested ('Caused by') exceptions.

          Daniel Beck added a comment - Full stack trace may be helpful if there are nested ('Caused by') exceptions.

          Mark Waite added a comment -

          Closing this bug as cannot reproduce

          Mark Waite added a comment - Closing this bug as cannot reproduce

            ndeloof Nicolas De Loof
            drammons David Ammons
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: