在TFS 2017中通过发布管理设置Maven构建 [英] Set up Maven build through Release Management in TFS 2017

查看:191
本文介绍了在TFS 2017中通过发布管理设置Maven构建的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,

我们已通过任务" Maven "在TFS中设置 Maven构建并提供了
POM.xml 文件的路径。当我们转到TFS中的构建选项卡并执行Maven构建时,它会成功执行。

We have setup the Maven build in TFS through the task "Maven" and supplied the path of POM.xml file. When we go to the build tab in TFS and execute the Maven build, it gets executed successfully.

我们已经在构建定义中的存储库选项卡下映射了代码所在的存储库,以及何时我们运行Maven构建任务,执行"获取源",将最新代码下载到代理机器。

We have mapped the Repository where code is there under the Repository tab in Build Definition, and when we run Maven build the task "Get Source" is executed which downloads the latest code to agent machine.

现在,我们需要将其设置为发布管理,以便它可以在多个环境中执行。

Now, we need to set this as a release management, so that it can be executed on multiple environment.

但是,在Release下没有Repository选项卡,并且没有"Get Source"任务。 ,因此无法找到存在代码的存储库。这就是错误导致失败的原因
"下载工件失败或者没有工件"。

But , under Release there is no Repository tab and there is no task of "Get Source" , so it cannot find the repository where code is there. That's why it gets failed with the error "Downloading artifacts failed OR No artifacts there".

请建议我们如何配置此设置,这样Maven构建就可以通过Release管理来执行。这将是一个很好的帮助。

Please suggest how we can configure this setup, so that Maven build can be executed through Release management. It would be a great help.

提前致谢,

Vaibhav

推荐答案

嗨  Vaibhav,

Hi Vaibhav,

感谢您在此发帖。

是的,发布定义与构建定义不同,没有Repository选项卡。

Yes, the release definition is not like build definition, there's no Repository tab.

我认为在您的发布定义中,您将其链接到构建定义以从构建工件获取源代码。如果您不想从构建中获取,则在链接工件源并选择源代码存储的TFVC / Git时。

I suppose that in your release definition, you link it to a build definition to get source from build artifacts. If you don't want to get from builds, when you link an artifact source and choose TFVC/Git where your source code stores.

祝你好运


这篇关于在TFS 2017中通过发布管理设置Maven构建的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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