Artifactory Jenkins插件下载命令不符合规范中的构建信息

我正在Jenkins管道中使用Jenkins JFrog Artifactory插件的

rtDownload

DSL块从Artifactory OSS下载一些工件。这就是我的rtDownload步骤的外观

      rtDownload (
        serverId: "artifactory",
        spec:
              """{
                "files": [
                  {
                    "pattern": "esb-dev-local/**",
                    "target": "artifacts/",          
                    "build": "TestJob/58"
                  }
               ]
              }"""
      )

但是，这似乎下载了与构建名称（TestJob）匹配的所有文件，并且没有按构建编号进行过滤。我可以在artifactory中正确地看到构建ID。关于我可能做错了什么有什么线索吗

这是詹金斯的输出

[Pipeline] rtDownload
Downloading artifacts using pattern: esb-dev-local/**
Beginning to resolve Build Info published dependencies.
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.pom'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.pom' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_58/<MASKED>-1.0_58.pom'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58-cfg.zip'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58-cfg.zip' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_58/<MASKED>-1.0_58-cfg.zip'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.pom'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.pom' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_58/<MASKED>-1.0_58.pom'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_32/<MASKED>-1.0_32.pom'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_32/<MASKED>-1.0_32.pom' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_32/<MASKED>-1.0_32.pom'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.jar'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.jar' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_58/<MASKED>-1.0_58.jar'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.jar'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_58/<MASKED>-1.0_58.jar' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_58/<MASKED>-1.0_58.jar'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_46/<MASKED>-1.0_46.pom'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_46/<MASKED>-1.0_46.pom' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_46/<MASKED>-1.0_46.pom'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/${projVersion}/<MASKED>-${projVersion}.pom'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/${projVersion}/<MASKED>-${projVersion}.pom' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/${projVersion}/<MASKED>-${projVersion}.pom'
Downloading 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_33/<MASKED>-1.0_33.pom'...
Successfully downloaded 'http://<MASKED>:8081/artifactory/esb-dev-local/<MASKED>/1.0_33/<MASKED>-1.0_33.pom' to '/var/lib/jenkins/workspace/<MASKED>/artifacts/<MASKED>/1.0_33/<MASKED>-1.0_33.pom'
Finished resolving Build Info published dependencies.

[Pipeline]下载
使用模式esb-dev-local下载工件/**
开始解析生成信息已发布的依赖项。
正在下载“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58.pom”。。。
已将“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58.pom”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_58/-1.0_58.pom”
正在下载“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58-cfg.zip”。。。
已成功将“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58-cfg.zip”下载到“/var/lib/jenkins/workspace//artifacts//1.0_58/-1.0_58-cfg.zip”
正在下载“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58.pom”。。。
已将“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58.pom”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_58/-1.0_58.pom”
正在下载“http://:8081/artifactory/esb dev local//1.0_32/-1.0_32.pom”。。。
已将“http://:8081/artifactory/esb dev local//1.0_32/-1.0_32.pom”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_32/-1.0_32.pom”
正在下载“http://:8081/artifactory/esb-dev-local//1.0\u 58/-1.0\u 58.jar”。。。
已将“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58.jar”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_58/-1.0_58.jar”
正在下载“http://:8081/artifactory/esb-dev-local//1.0\u 58/-1.0\u 58.jar”。。。
已将“http://:8081/artifactory/esb dev local//1.0_58/-1.0_58.jar”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_58/-1.0_58.jar”
正在下载“http://:8081/artifactory/esb dev local//1.0_46/-1.0_46.pom”。。。
已将“http://:8081/artifactory/esb dev local//1.0_46/-1.0_46.pom”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_46/-1.0_46.pom”
正在下载“http://:8081/artifactory/esb-dev-local/${projVersion}/-${projVersion}.pom”。。。
已成功将“http://:8081/artifactory/esb-dev-local/${projVersion}/-${projVersion}.pom”下载到“/var/lib/jenkins/workspace//artifacts/${projVersion}/-${projVersion}.pom”
正在下载“http://:8081/artifactory/esb-dev-local//1.0\u 33/-1.0\u 33.pom”。。。
已将“http://:8081/artifactory/esb dev local//1.0_33/-1.0_33.pom”成功下载到“/var/lib/jenkins/workspace//artifacts//1.0_33/-1.0_33.pom”
已完成解析生成信息发布的依赖项。

下载的工件与属于请求构建的工件（名称和编号）相等（通过校验和）

在多个工件与构建中列出的校验和匹配的场景中，正确的下载路径由工件的属性（构建名称和编号）确定。但是，由于artifactoryoss不支持artifacts属性，因此返回的路径不确定

---

这就是为什么您会看到一些从其他构建编号的路径下载的工件。这些工件已正确下载，但下载路径似乎不同

下载的工件与属于请求构建的工件（名称和编号）相等（通过校验和）

在多个工件与构建中列出的校验和匹配的场景中，正确的下载路径由工件的属性（构建名称和编号）确定。但是，由于artifactoryoss不支持artifacts属性，因此返回的路径不确定

---

这就是为什么您会看到一些从其他构建编号的路径下载的工件。这些工件已正确下载，但下载路径似乎不同

您可以尝试从json文件使用specPath源代码

您可以尝试从json文件使用specPath源代码

只需一条旁注-“*”可以用作通配符，因此一条就足够了，并且与几个连续的字符完全相同（可能只是输入错误，但以防万一）。@Prostagna是否也匹配“/”字符？有时，

***

用于匹配深层文件夹结构。只需一条旁注-“*”就可以作为通配符使用，因此一条注释就足够了，并且与几个连续的注释完全相同（可能只是输入错误，但以防万一）。@Prostagna是否也匹配“/”字符？有时，

**

用于匹配深层文件夹结构。我猜就是这样。我从Artifactory中删除了“额外”工件，该问题似乎已经消失，并继续为后续构建工作。@R4nd0mbr1ck很高兴这有帮助。在cli中签出discard builds命令，该命令可能有助于删除旧的不需要的生成。请将答案向上投票，以帮助其他人找到它，谢谢！我想就是这样。我从Artifactory中删除了“额外”工件，该问题似乎已经消失，并继续为后续构建工作。@R4nd0mbr1ck很高兴这有帮助。在cli中签出discard builds命令，该命令可能有助于删除旧的不需要的生成。请将答案向上投票，以帮助其他人找到它，谢谢！