Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: git-plugin
-
Labels:None
-
Environment:Jenkins 1.651.3, ubuntu 14.04, Oracle Java 7
-
Similar Issues:
Description
Once I updated to 2.5.1, I couldn't index the branches anymore in my pipeline projects which use github as their source control rather than git. Going back to 2.5.0 makes it work again. It also works if I use the "git" section instead of the "github" section for source control.
The exception in the log is
Executor threw an exception java.lang.AbstractMethodError: jenkins.plugins.git.AbstractGitSCMSource.getExtensions()Ljava/util/List; at jenkins.plugins.git.AbstractGitSCMSource.build(AbstractGitSCMSource.java:305) at jenkins.scm.api.SCMSource.build(SCMSource.java:283) at jenkins.branch.MultiBranchProject.newBranch(MultiBranchProject.java:267) at jenkins.branch.MultiBranchProject.access$000(MultiBranchProject.java:82) at jenkins.branch.MultiBranchProject$1.observe(MultiBranchProject.java:297) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.doRetrieve(GitHubSCMSource.java:285) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:256) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:146) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)
Attachments
Issue Links
- relates to
-
JENKINS-31924 GitSCMSource should offer extensions
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | support_2016-07-04_17.46.31.zip [ 33206 ] |
Summary | git plugin 2.5.1 breaks multibranch pipeline | git plugin 2.5.1 breaks multibranch pipeline if using github source control |
Description |
Once I updated to 2.5.1, I couldn't index the branches anymore in my pipeline projects. Going back to 2.5.0 makes it work again. The exception in the log is {noformat} Executor threw an exception java.lang.AbstractMethodError: jenkins.plugins.git.AbstractGitSCMSource.getExtensions()Ljava/util/List; at jenkins.plugins.git.AbstractGitSCMSource.build(AbstractGitSCMSource.java:305) at jenkins.scm.api.SCMSource.build(SCMSource.java:283) at jenkins.branch.MultiBranchProject.newBranch(MultiBranchProject.java:267) at jenkins.branch.MultiBranchProject.access$000(MultiBranchProject.java:82) at jenkins.branch.MultiBranchProject$1.observe(MultiBranchProject.java:297) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.doRetrieve(GitHubSCMSource.java:285) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:256) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:146) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) {noformat} |
Once I updated to 2.5.1, I couldn't index the branches anymore in my pipeline projects which use github as their source control rather than git. Going back to 2.5.0 makes it work again. It also works if I use the "git" section instead of the "github" section for source control. The exception in the log is {noformat} Executor threw an exception java.lang.AbstractMethodError: jenkins.plugins.git.AbstractGitSCMSource.getExtensions()Ljava/util/List; at jenkins.plugins.git.AbstractGitSCMSource.build(AbstractGitSCMSource.java:305) at jenkins.scm.api.SCMSource.build(SCMSource.java:283) at jenkins.branch.MultiBranchProject.newBranch(MultiBranchProject.java:267) at jenkins.branch.MultiBranchProject.access$000(MultiBranchProject.java:82) at jenkins.branch.MultiBranchProject$1.observe(MultiBranchProject.java:297) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.doRetrieve(GitHubSCMSource.java:285) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:256) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:146) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) {noformat} |
Priority | Major [ 3 ] | Blocker [ 1 ] |
Assignee | Mark Waite [ markewaite ] | Oleg Nenashev [ oleg_nenashev ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Link |
This issue relates to |
Workflow | JNJira [ 173126 ] | JNJira + In-Review [ 199399 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Thanks for reporting the problem. Can you provide more details on your system configuration? A support bundle would be ideal, since it provides lots of information in a single package that is easy to collect and easy to upload?
My reading of that exception in the JDK 7 javadoc shows
. I think that must mean that I inadvertently changed a method signature of a method in a class that extends an Abstract class, or I changed an Abstract method definition.I'm especially perplexed why I didn't see the problem in my testing before release, since I tested with JDK 8 + Jenkins 1.651.3 + Debian and I tested with JDK 7 + Jenkins 1.609.3 + Debian.
After installing the new version of the git plugin, did you restart your Jenkins instance?
There is a change/addition from Hiroyuki Wada in AbstractGitSCMSource to add many more git options to the multi-branch plugin and the literate plugin (and anything else that uses the SCMSource interface). That change, and its successors 1, 2, 3, and the merge 4 (add tests, refine the code, etc.) worked well in my tests.
Are any of your pipeline plugins out of date?
Any other areas which you think might have relevant differences?