上传的项目图片:“Jenkins Artifactory插件”
  1. Jenkins Artifactory插件
  2. hap - 828

管道Gradle不能与守护进程一起工作

    XML 可打印的

    细节

    • 类型: 错误
    • 状态: Resolved
      A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">解决
    • 解决方法: 完成
    • 影响版本/ s: 2.7.2
    • 修复版本/ s: 2.8.0
    • 组件/ s: Gradle
    • 标签:
      没有一个

      描述

      当你用daemon运行Gradle时,只有第一个作业会运行,但第二个及以上的作业会失败。复制步骤:

      1.创建以下管道脚本:

      节点{阶段“克隆”git url:“https:/ / github.com/JFrogDev/project-examples.git”阶段“定义新艺术”defserver = Artifactory.server(“-555800408 @1461342837804”)阶段“Gradle配置”gradleinstall = Artifactory.newGradleBuild()工具=“G2”gradleInstallation.deployer回购:“堡垒”, server: server gradleInstallation。解析器回购:“jcenter-virtual”、server:服务器阶段“双性恋”def buildInfo = Artifactory.newBuildInfo() buildInfo.env.capture =真正的阶段“exc gradle”gradleInstallation.run rootDir:“gradle-examples / 4 / gradle-example-ci-server /”构建文件:“build.gradle”任务:'clean artifactoryPublish——daemon 'buildInfo: buildInfo// gradleInstallation.run rootDir:“gradle-examples / 4 / gradle-example-ci-server /”构建文件:“build.gradle”任务:'clean artifactoryPublish——no-daemon 'buildInfo: buildInfo服务器。publishBuildInfo buildInfo}

      2.第一份工作将会奏效。
      3.运行第二个作业,它将失败,无法读取构建信息:

      错误:无法读取:/处生成的构建信息var/folders/82/8zx542jj35d20c_trfj95pwd093zmm/T/generated.build.info7897905422423739539.json [Pipeline]} [Pipeline]/ /节点[管道]管道的末端。运行RunnerAbortedException美元org.jfrog.hudson.pipeline.Utils.getGeneratedBuildInfo (Utils.java: 186)美元org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild Execution.run (ArtifactoryGradleBuild.java: 125)美元org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild Execution.run (ArtifactoryGradleBuild.java: 95) org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start (AbstractSynchronousStepExecution.java: 40) org.jenkinsci.plugins.workflow.cps.DSL.invokeStep (DSL.java: 184)在org.jfrog.hudson.pipeline.types.GradleBuild.run(GradleBuild.java:66) at org.jfrog.hudson.pipeline.types.GradleBuild$run。在org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at .codehaus.groovy.runtime. callsitearray.defaultcall (CallSiteArray.java:42) at .codehaus.groovy.runtime.callsite. abstractcallsite .call(AbstractCallSite.java:108)在com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:16) at ___cps。com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun. reflection . generatedmethodaccessor232。调用(未知源)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.CollectionLiteralBlock ContinuationImpl.dispatch (CollectionLiteralBlock.java: 55) com.cloudbees.groovy.cps.impl.CollectionLiteralBlock ContinuationImpl.item美元(CollectionLiteralBlock.java: 45)sun.reflect.GeneratedMethodAccessor198。在com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:33) at . com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at . com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) .调用(Method.java:498) at .lang. reflection . method .invoke(Method.java:498) at . com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)com.cloudbees. groovy.cps.imp.localvariableblock . evallvalue (LocalVariableBlock.java:22) at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java: 55) at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:324) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 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.线程.run (线程.java:745) Finished: failed

      作为一种解决方案,需要添加——no-daemon标志来不使用守护进程

        附件

          问题的链接

            活动

              受让人:
              tamirh塔米尔·哈达德[X](非活跃人士)
              记者:
              alexeivAlexei Vainshtein [X](非活跃)
              投票:
              1 为这个问题投票
              观察人士:
              3. 开始收看本期节目

                日期

                创建:
                更新:
                解决: