Status: Open (View Workflow)
Pipeline (workflow-plugin) 1.13
Polling error on a Pipeline Job:
java.lang.AbstractMethodError: you must override the new overload of compareRemoteRevisionWith at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:375) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:507) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:526) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:555) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
- is related to
JENKINS-24141 SCM with non-AbstractProject, revisited
- relates to
JENKINS-27717 CVS/Workflow integration
Generally you should check for deprecation warnings in SCM subclasses.
Sorry jglick, who is that comment aimed at? Is there an issue with the pull request, or are you implying that plugin maintainers should be checking the compatibility of their plugin with each Jenkins version?
What needs to happen so I can use CVS polling from a pipeline?
As a workaround, I can use cron and trigger a build via HTTP if changes found, but that is a hack.
P.S. The link to the "compatibility guide" on https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/README.md returns a 404.
I'm using the plugin modified by the pull request above for five months now in production and the CVS polling works very well.
valones It looks like the CVS plugin maintainer will not create a new major version with your patch. Would you be willing to publish your fork to Jenkins plugin repo under a new name?
mkbucc it's not that I'm unprepared to accept the pull request or perform a release; it's that I no longer use CVS so have no particular way of checking the changes or testing releases. If you'd like to have this change incorporated or released then feel free to take on ownership of the CVS plugin!
Sorry mkbucc, I have no time now to maintain a plugin. My company is moving from CVS to Git and its usage is becoming ever smaller, probably I will not go make further changes in plugin.
I submit a pull request (https://github.com/jenkinsci/cvs-plugin/pull/41) to fix this.