使用连续集成构建标记 [英] Building tags using Continuous Integration

问题描述

如何建立持续整合标记而不是分支的做法？

How could I establish practice of continuously integrating tags instead of branches?

我有以下结构的标签库目录（此处是存储库结构的更详细说明）：

I have following structure of tags repository directory (here is more detailed explanation of the repository structure):

/tags
    /builds
        /PA
        /A
        /B
    /releases
        /AR
        /BR
        /RC
        /ST

我想配置我的连续集成工具（它可以是来自CruiseControl，Hudson

I would like to configure my continuous integration tool (it could be anything from CruiseControl, Hudson and Jenkins to TeamCity) to build latest tag if it has been created in either of those folders.

例如，如果结构已更改并且标记 1.x.0 出现在 PA 目录中，我想在 1.x下触发构建源代码。 0 标记：

For example, if structure has changed and tag 1.x.0 has appeared in PA directory, I want to trigger building of source code under 1.x.0 tag:

/tags
    /builds
        /PA
            /1.x.0 -> triggers build
        /A
        /B
    /releases
        /AR
        /BR
        /RC
        /ST

是否可以使用任何现有的持续集成工具在标签下构建源代码，或者我应该为此目的编写自己的插件？

Is it possible to build source under tags with any of the existing continuous integration tools or I should write my own plugin for that purpose?

推荐答案

使用Jenkins：使用定期作业检查新标签，然后使用参数化触发器插件，以标签作为参数启动作业。作业将手动更新到标记和构建。

With Jenkins: use a periodic job to check for new tags, then use the Parametrized Trigger Plugin to kick off your job with the tag as a parameter. The job will manually update to the tag and build.

这篇关于使用连续集成构建标记的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！