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

当没有定义部署器时,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: 3.5.0
    • 修复版本/ s: 3.6.0
    • 组件/ s: Gradle
    • 环境:

      Ubuntu仿生Docker奴隶
      Ubuntu仿生主机系统
      詹金斯v2.164.1
      Gradle v6.2.1

    • 回归:
      是的

      描述

      从3.4.1版本升级到3.5.0版本的Artifactory插件打破了Artifactory Gradle解析器/部署器的步骤,似乎它认为repo名称是空的(https://github.com/jenkinsci/artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/pipeline/common/types/deployers/GradleDeployer.java#L49

      下面是失败的管道阶段:

      阶段(初始化它的){步骤{rtGradleResolver(id:“artifactory-gradle-resolver”serverId:“VonLatvala Artifactory”回购协议:“gradle-remote”,) rtGradleDeployer(id:“artifactory-gradle-deployer”serverId:“VonLatvala Artifactory”回购协议:“cloudsaber-client”,) rtGradleRun(usesPlugin:真正的, tool: GRADLE_TOOL, useWrapper:构建文件:“build_ci.gradle”任务:“init”resolverId:“artifactory-gradle-resolver”,)}}

      下面是errormessage + stacktrace:

      java.io.IOException:部署器应该设置为任意一个“回购”或两个“releaseRepo”“snapshotRepo”在org.jfrog.hudson.pipeline.common.types.deployers.GradleDeployer.getDetails(GradleDeployer.java:32)在org.jfrog.hudson.pipeline.common.types.deployers.GradleDeployer.getContextBuilder(GradleDeployer.java:162)在org.jfrog.hudson.pipeline.common.executors.EnvExtractor.createPublisherContext(EnvExtractor.java:54) at .org.jfrog.hudson.pipeline.common.executors.EnvExtractor.createArtifactoryClientConfiguration(EnvExtractor.java:75) at org.jfrog.hudson.pipeline.common.executors.EnvExtractor.execute(EnvExtractor.java:64)原因:在org.jfrog.hudson.pipeline.common.executors.GradleExecutor.execute(GradleExecutor.java:66) at org.jfrog.hudson.pipeline.declarative.steps.gradle.GradleStep$Execution.run(GradleStep.java:135) at org.jfrog.hudson.pipeline.declarative.steps.gradle.GradleStep$Execution.run(GradleStep.java:109) at .jfrog.hudson.pipeline.declarative.steps. gradlestep $Execution.run(GradleStep.java:109org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution 1美元1.美元(AbstractSynchronousNonBlockingStepExecution.java: 47)打电话hudson.security.ACL.impersonate (ACL.java: 290) org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution 1.美元(AbstractSynchronousNonBlockingStepExecution.java: 44)运行在java.base / java.util.concurrent.Executors RunnableAdapter.call美元(Executors.java: 515) java.base / java.util.concurrent.FutureTask.run (FutureTask.java: 264)java.base/java.util.concurrent.ThreadPoolExecutor. runworker (ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java。线程.run (线程. java: 834)

      正如标题所述,似乎hap - 1174引入了这个bug。

      使用插件版本v3.4.1的Build #10
      使用插件版本v3.5.0构建#11
      使用插件版本v3.4.1构建#12

      管道的例子

        附件

          活动

            受让人:
            yahaviYahav伊扎克。
            记者:
            VonLatvalaAxel Latvala(非活跃)
            投票:
            0 为这个问题投票
            观察人士:
            2 开始收看本期节目

              日期

              创建:
              更新:
              解决: