作者:rvu2352314 | 来源:互联网 | 2023-09-23 02:59
ImusingtheArtifactorypluginforTeamCitytostoreartifactsfromourbuilds.Theplugin,howeve
I'm using the Artifactory plugin for TeamCity to store artifacts from our builds. The plugin, however, does some things that seem to me to be quite odd, and not TeamCity-ish at all.
我正在使用TeamCity的Artifactory插件来存储构建中的工件。然而,插件做了一些在我看来很奇怪的事情,而不是TeamCity-ish。
The plugin adds a new section to the settings for each build step in my build configuration. This section allows me to specify artifacts to be stored in Artifactory. What is odd, however, is that these settings are particular to each build step; this means that if my build has two build steps, and I set up the first build step to store artifacts, and then view the settings for the second build step, the plugin will not appear to be configured there.
该插件为我的构建配置中的每个构建步骤的设置添加了一个新部分。本节允许我指定要存储在Artifactory中的工件。然而,奇怪的是,这些设置对于每个构建步骤都是特定的;这意味着如果我的构建有两个构建步骤,并且我设置了第一个构建步骤来存储工件,然后查看第二个构建步骤的设置,那么该插件似乎不会在那里配置。
Further confusing the issue is that the documentation specifies that the plugin works with "most" build runner types, and lists several examples: "Maven2, Maven 3, Ivy/Ant (with Ivy modules support), Gradle , NAnt, MSBuild, FxCop and Ipr."
进一步混淆问题的是文档指定插件使用“大多数”构建运行器类型,并列出了几个示例:“Maven2,Maven 3,Ivy / Ant(支持常春藤模块),Gradle,NAnt,MSBuild,FxCop和知识产权“。
My question is, then, which build step should I configure Artifactory for? What if I configure it for a build step that isn't on the list of "working" build runners? Why does the plugin allow/require me to configure it multiple times?
我的问题是,我应该为Artifactory配置哪个构建步骤?如果我将其配置为不在“工作”构建运行器列表中的构建步骤,该怎么办?为什么插件允许/要求我多次配置它?
It seems to me that the Artifactory plugin should instead add a new build runner, i.e. "Deploy artifacts to Artifactory", which would give me one supported place to configure it.
在我看来,Artifactory插件应该添加一个新的构建运行器,即“将工件部署到Artifactory”,这将给我一个支持的位置来配置它。
1 个解决方案