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

GitStep is missing its descriptor with example build

    Details

    • Similar Issues:

      Description

      I've been testing the waters of Jenkins 2 as I'm interested in the pipeline workthrough but hit a snag.

      1.

      docker run -p 8080:8080 -p 50000:50000 --name jenkins2 jenkinsci/jenkins:2.8

      2. Log in, create account, etc
      3. Create Pipeline project
      4. Configure
      5. In Pipeline section, "try sample pipeline" > "Github + Maven"

      Behaviour:

      java.lang.AssertionError: class org.jenkinsci.plugins.workflow.steps.scm.GitStep is missing its descriptor
      	at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1304)
      

      I get the same error when attempting to point to my own github repo.

        Attachments

          Issue Links

            Activity

            Hide
            notflorian Florian Fauvarque added a comment -

            I also have the exact same issue with the 2.8 docker image.

            Show
            notflorian Florian Fauvarque added a comment - I also have the exact same issue with the 2.8 docker image.
            Hide
            nigel_charman nigel_charman added a comment -

            Do you have Git installed?

            The sample pipeline docs include the step:

            > 2. Only if you do not have Git installed on your Jenkins server: click Delete Git on the default Git installation and Add Git » JGit to replace it.

            I had this exact error message. In my case, I had installed Git on the Jenkins server, but failed to restart Jenkins. After restarting Jenkins it was fixed.

            Show
            nigel_charman nigel_charman added a comment - Do you have Git installed? The sample pipeline docs include the step: > 2. Only if you do not have Git installed on your Jenkins server: click Delete Git on the default Git installation and Add Git » JGit to replace it. I had this exact error message. In my case, I had installed Git on the Jenkins server, but failed to restart Jenkins. After restarting Jenkins it was fixed.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                crummy malcolm crum
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: