Jenkins 更新后出现错误:java.lang.NoSuchMethodError:在步骤中找不到这样的 DSL 方法“管道" [英] Getting error after Jenkins update: java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps

查看:79
本文介绍了Jenkins 更新后出现错误:java.lang.NoSuchMethodError:在步骤中找不到这样的 DSL 方法“管道"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我将 Jenkins 版本从 2.224 更新到 2.234 以及所有插件到最新版本后,我的 Jenkins 管道出现故障.

下面是我的管道脚本,它在较旧的 Jenkins 和较旧的插件上运行良好.

随着 Jenkins 和插件更新,管道出现故障.

 管道 {代理 无阶段{阶段(检查参数"){脚步 {echo 在管道中"脚本 {echo "开始条件检查";}}}}}

以上只是一个示例,因为实际的管道脚本非常庞大,我不想让读者感到困惑.

运行管道时出现以下错误

 [Pipeline] 管道开始[管道] 管道结束java.lang.NoSuchMethodError: [ansiColor, ansiblePlaybook, ansibleTower, ansibleTowerProjectRevision, ansibleTowerProjectSync, ansibleVault, archive, bat, catchError, checkout, deleteDir, dir, dockerFingerprintFrom, dockerFingerprintFrom, dockerFingerprint, email, emailextrecipients, error, fileExists, findBuildScans, getContext, git, input, isUnix, junit, library, libraryResource, load, lock, mail, node, parallel, powershell, properties, publishHTML, pwd, pwsh, readFile, readTrusted, resolveScm, retry, sh, sleep, stage, stash, step, svn, task, ti​​meout, tm, tool, unarchive, unarchive, unstash, waitUntil, warnError, withContext, withCredentials, withDockerContainer, withDockerRegistry, withDockerServer, withEnv, withGradle, wrap, writeFile, ws] 或符号 [all、always、ant、antFromApache、antOutcome、antTarget、apiToken、架构、archiveArtifacts、artifactManager、attach、authorizationMatrix、batchFile、booleanParam、brokenBuildSuspects、brokenTestsSuspects、buildButton、buildDiscarder、buildDiscarders、buildFailureAnalyzer、caseInsensitive、caseSensitive、证书、选择、choiceParam、cleanWs、时钟、命令、凭据、cron、面包屑、cssText、cssUrl、罪魁祸首、defaultFolderConfiguration、defaultView、需求、开发人员、disableConcurrentBuilds、disableResume、docker、dockerCert、dockerfile、下游、哑、耐久性提示、envInject、envVars、faviconUrl、文件、fileParam、filePath、指纹、frameOptions、freeStyle、freeStyleJob、fromScm、fromSource、ftpPublisher、git、gitBranchDiscovery、gitBranchDiscovery、gitBranchDiscovery、gitHubposityBHubchBranch、或gitHubForkDiscovery, gitHubPullRequestDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, githubFilter, hyperPush, hyperPush源,jdk,jdkInstaller,jgit,jgitapache,jnlp,jobBuildDiscarder,jobName,jsUrl,lastDuration,lastFailure,lastGrantedAuthorities,lastStable,lastSuccess,legacy,legacySCM,列表,本地,位置,logRotator,loggedInUsersCanDoAnything,mailer,masterBuild,mavenmavenErrors、mavenMojos、mavenWarnings、modernSCM、myView、newContainerPerStage、nodeProperties、nonInheriting、none、overrideIndexTriggers、paneStatus、parameterizedCron、参数、密码、模式、永久、管道模型、管道模型泊坞窗、管道触发器、纯文本、插件、pollSCM、projectNamingStrategy、proxy、queueItemAuthenticator、quietPeriod、rateLimitBuilds、收件人、请求者、resourceRoot、run、runParam、sSHLauncher、schedule、scmRetryCount、scriptApproval、scriptApprovalLink、搜索、安全、shell、简单主题插件、simpleBuildDiscarder、slave、sourceRegexFilter、sourceWildcardssh、sshPublicKey、sshPublisher、sshPublisherDesc、sshTransfer、sshUserPrivateKey、标准, status, string, stringParam, swapSpace, teamSlugFilter, text, textParam, timezone, tmpSpace, toolLocation, unsecured, upstream, upstreamDevelopers, userSeed, usernameColonPassword, usernamePassword, validatingString, viewsTabBar, weather, withAnt, zfs, zip] 或全局变量 [currentBuild,码头工人,环境,参数,scm]在 org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:202)在 org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)在 sun.reflect.GeneratedMethodAccessor232.invoke(未知来源)在 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)在 java.lang.reflect.Method.invoke(Method.java:498)在 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)在 groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)在 groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)在 groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)在 org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)在 org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)在 org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)在 org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:163)在 org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)在 org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157)在 org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:142)在 org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)在 org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)在 com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)在 WorkflowScript.run(WorkflowScript:1)在 ___cps.transform___(本机方法)在 com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)在 com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)在 com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)在 sun.reflect.GeneratedMethodAccessor231.invoke(未知来源)在 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)在 java.lang.reflect.Method.invoke(Method.java:498)在 com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)在 com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)在 com.cloudbees.groovy.cps.Next.step(Next.java:83)在 com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)在 com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)在 org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)在 org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)在 com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)在 org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)在 org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)在 org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)在 org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:400)在 org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)在 org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312)在 org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276)在 org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)在 java.util.concurrent.FutureTask.run(FutureTask.java:266)在 hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)在 jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)在 jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)在 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)在 java.util.concurrent.FutureTask.run(FutureTask.java:266)在 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)在 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)在 java.lang.Thread.run(Thread.java:748)完成:失败

Plugin ManagerInstalled 选项卡下显示的管道插件当前更新的最新版本如下:我发现缺少的一件事是早先在已安装的插件下可见的管道:2.6 版

根据我的研究,我下载了 https://plugins.jenkins.io/workflow-aggregator/ hpi 文件,但是,当我在离线模式下安装此插件时,它尝试拉取依赖项,例如 Pipeline Milestone Step 等.

获取此 hpi 文件及其依赖项是否可以解决我的问题?请澄清.

 构建流水线插件此插件呈现通常形成构建管道的上游和下游连接的作业.此外,它还能够为在执行前需要干预的作业定义手动触发器,例如Jenkins 之外的审批流程.1.5.8交付管道插件此插件可视化交付管道(具有上游/下游依赖项的作业)1.4.2管道图分析插件提供 REST API 以访问管道和管道运行数据.1.10管道:API定义流水线 API 的插件.2.40管道:基本步骤管道的常用步骤.2.20管道:声明性扩展点 API声明式管道中使用的扩展点的 API.1.6.0管道:GitHub Groovy 库允许从 GitHub 动态加载 Pipeline Grovy 库.1.0管道:Groovy基于 Groovy 脚本的延续传递风格转换的流水线执行引擎.2.80管道:输入步骤添加管道步骤输入以等待人工输入或批准.2.11管道:工作为管道定义新的作业类型并提供其通用用户界面.2.39管道:模型 API声明式管道的模型 API.1.6.0管道:多分支通过自动对来自不同分支的构建进行分组,增强 Pipeline 插件以更好地处理分支.2.21管道:节点和进程管道步骤锁定代理和工作区,并运行可能在 Jenkins 重启或从设备重新连接后仍然存在的外部进程.2.35管道:REST API 插件提供 REST API 以访问管道和管道运行数据.2.13流水线:SCM 步骤添加流水线步骤以检出或更新来自各种 SCM(版本控制)的工作源.2.11管道:共享 Groovy 库管道脚本的共享库.2.16管道:阶段步骤添加流水线步骤阶段以描绘构建的各个部分.2.3管道:舞台视图插件管道舞台视图插件.2.13管道:步骤 API用于异步构建步骤原语的 API.2.22管道:支持 API构建流水线插件的常见实用程序实现3.4

我没有互联网连接,我必须手动复制插件.

我确实在一些插件旁边看到了降级按钮.但是,不希望由于漏洞和错误修复而降级.

能否请您提出一些解决方案?

解决方案

问题是未安装管道插件.因此我下载了管道插件版本 2.6

https://plugins.jenkins.io/workflow-aggregator/

然后我下载了如下依赖项:

https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/https://updates.jenkins.io/download/plugins/pipeline-milestone-step/https://plugins.jenkins.io/pipeline-model-definition/https://plugins.jenkins.io/pipeline-model-declarative-agent/https://plugins.jenkins.io/pipeline-stage-tags-metadata/

在离线模式下一一安装,问题解决.

My Jenkins pipeline is failing after I updated by Jenkins version from 2.224 to 2.234 along with all the plugins to the latest version.

Below is my pipeline script which was working fine with older Jenkins and older plugins.

With Jenkins and plugin update, the pipeline is failing.

    pipeline { 
        agent none    
        stages {
             stage ("Check Parameters") { 
                   steps {
                       echo "In pipeline"
                          script {
                            echo "Start condition check"
                          }
                    }
                }
            }
    }

The above is just a sample as the actual pipeline script is quite vast and I did not wish to confuse the readers.

I get the following Error when i run the pipeline

    [Pipeline] Start of Pipeline
    [Pipeline] End of Pipeline
    java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiColor, ansiblePlaybook, ansibleTower, ansibleTowerProjectRevision, ansibleTowerProjectSync, ansibleVault, archive, bat, catchError, checkout, deleteDir, dir, dockerFingerprintFrom, dockerFingerprintRun, dockerNode, echo, emailext, emailextrecipients, error, fileExists, findBuildScans, getContext, git, input, isUnix, junit, library, libraryResource, load, lock, mail, node, parallel, powershell, properties, publishHTML, pwd, pwsh, readFile, readTrusted, resolveScm, retry, sh, sleep, stage, stash, step, svn, task, timeout, tm, tool, unarchive, unstable, unstash, waitUntil, warnError, withContext, withCredentials, withDockerContainer, withDockerRegistry, withDockerServer, withEnv, withGradle, wrap, writeFile, ws] or symbols [all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, attach, authorizationMatrix, batchFile, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildButton, buildDiscarder, buildDiscarders, buildFailureAnalyzer, caseInsensitive, caseSensitive, certificate, choice, choiceParam, cleanWs, clock, command, credentials, cron, crumb, cssText, cssUrl, culprits, defaultFolderConfiguration, defaultView, demand, developers, disableConcurrentBuilds, disableResume, docker, dockerCert, dockerfile, downstream, dumb, durabilityHint, envInject, envVars, faviconUrl, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, ftpPublisher, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubExcludeArchivedRepositories, gitHubForkDiscovery, gitHubPullRequestDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, gradle, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobBuildDiscarder, jobName, jsUrl, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, mailer, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, newContainerPerStage, nodeProperties, nonInheriting, none, overrideIndexTriggers, paneStatus, parameterizedCron, parameters, password, pattern, permanent, pipeline-model, pipeline-model-docker, pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, rateLimitBuilds, recipients, requestor, resourceRoot, run, runParam, sSHLauncher, schedule, scmRetryCount, scriptApproval, scriptApprovalLink, search, security, shell, simple-theme-plugin, simpleBuildDiscarder, slave, sourceRegexFilter, sourceWildcardFilter, ssh, sshPublicKey, sshPublisher, sshPublisherDesc, sshTransfer, sshUserPrivateKey, standard, status, string, stringParam, swapSpace, teamSlugFilter, text, textParam, timezone, tmpSpace, toolLocation, unsecured, upstream, upstreamDevelopers, userSeed, usernameColonPassword, usernamePassword, validatingString, viewsTabBar, weather, withAnt, zfs, zip] or globals [currentBuild, docker, env, params, scm]
        at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:202)
        at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
        at sun.reflect.GeneratedMethodAccessor232.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
        at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
        at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:163)
        at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
        at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157)
        at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:142)
        at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)
        at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)
        at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
        at WorkflowScript.run(WorkflowScript:1)
        at ___cps.transform___(Native Method)
        at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
        at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
        at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
        at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
        at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)
        at com.cloudbees.groovy.cps.Next.step(Next.java:83)
        at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
        at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
        at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
        at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
        at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
        at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
        at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
        at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:400)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312)
        at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276)
        at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
    Finished: FAILURE

The current updated latest versions of pipeline plugin showing under Installed tab of Plugin Manager is below: The one thing that I see missing that was visible earlier under installed plugins is Pipeline: version 2.6

Upon my research I downloaded https://plugins.jenkins.io/workflow-aggregator/ hpi file, however, when i install this plugin in offline mode it tried to pull dependencies like Pipeline Milestone Step etc.

Is getting this hpi file and its dependencies installed the solution to my problem? Please clarify.

    Build Pipeline Plugin
    This plugin renders upstream and downstream connected jobs that typically form a build pipeline. In addition, it offers the ability to define manual triggers for jobs that require intervention prior to execution, e.g. an approval process outside of Jenkins.
    1.5.8       
        
    Delivery Pipeline Plugin
    This plugin visualize Delivery Pipelines (Jobs with upstream/downstream dependencies)
    1.4.2       
            
    Pipeline Graph Analysis Plugin
    Provides a REST API to access pipeline and pipeline run data.
    1.10        
        
    Pipeline: API
    Plugin that defines Pipeline API.
    2.40        
        
    Pipeline: Basic Steps
    Commonly used steps for Pipelines.
    2.20    
        
    Pipeline: Declarative Extension Points API
    APIs for extension points used in Declarative Pipelines.
    1.6.0       
        
    Pipeline: GitHub Groovy Libraries
    Allows Pipeline Grrovy libraries to be loaded on the fly from GitHub.
    1.0     
        
    Pipeline: Groovy
    Pipeline execution engine based on continuation passing style transformation of Groovy scripts.
    2.80        
        
    Pipeline: Input Step
    Adds the Pipeline step input to wait for human input or approval.
    2.11        
        
    Pipeline: Job
    Defines a new job type for pipelines and provides their generic user interface.
    2.39    
        
    Pipeline: Model API
    Model API for Declarative Pipeline.
    1.6.0       
        
    Pipeline: Multibranch
    Enhances Pipeline plugin to handle branches better by automatically grouping builds from different branches.
    2.21        
        
    Pipeline: Nodes and Processes
    Pipeline steps locking agents and workspaces, and running external processes that may survive a Jenkins restart or slave reconnection.
    2.35        
        
    Pipeline: REST API Plugin
    Provides a REST API to access pipeline and pipeline run data.
    2.13        
        
    Pipeline: SCM Step
    Adds a Pipeline step to check out or update working sources from various SCMs (version control).
    2.11    
        
    Pipeline: Shared Groovy Libraries
    Shared libraries for Pipeline scripts.
    2.16    
        
    Pipeline: Stage Step
    Adds the Pipeline step stage to delineate portions of a build.
    2.3     
        
    Pipeline: Stage View Plugin
    Pipeline Stage View Plugin.
    2.13        
        
    Pipeline: Step API
    API for asynchronous build step primitive.
    2.22        
        
    Pipeline: Supporting APIs
    Common utility implementations to build Pipeline Plugin
    3.4     

I do not have internet connectivity and I have to copy the plugins manually.

I do see the downgrade button next to a few plugins. However, do not wish to downgrade due to vulnerability and bug fixes.

Can you please suggest some solution, please?

解决方案

The issue was pipeline plugin was not installed. Thus I downloaded the pipeline plugin version 2.6

https://plugins.jenkins.io/workflow-aggregator/

I then downloaded the dependencies as below:

https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/
https://updates.jenkins.io/download/plugins/pipeline-milestone-step/
https://plugins.jenkins.io/pipeline-model-definition/
https://plugins.jenkins.io/pipeline-model-declarative-agent/
https://plugins.jenkins.io/pipeline-stage-tags-metadata/ 

Installed them one by one in offline mode and the issue was resolved.

这篇关于Jenkins 更新后出现错误:java.lang.NoSuchMethodError:在步骤中找不到这样的 DSL 方法“管道"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆