如何使用 Continuum 从多个分支进行构建
我有一个使用 Maven 和 Continuum 构建的项目。我们有几个发布分支，其中大多数都已停用，但如果出现问题，任何一个分支都可以恢复。
我的问题是，向 Continuum 添加分支是非常重量级的；到目前为止，我发现的最好方法是将每个分支添加为单独的项目，但这涉及合理的设置量。由于我们不经常发布版本，这很好，但我希望能够针对短期功能分支运行 Continuum，并且我不想每次都手动设置所有内容。
I've got a project which is built using Maven and Continuum. We've got several release branches, most of which are in retirement but any could conceivably be resurrected if an issue comes up.
My problem is that adding branches to Continuum is very heavyweight; the best method I've found so far is to add each branch as a separate project, but that involves a reasonable amount of setup. As we don't make releases all that often, this is fine, but I'd like the ability to run Continuum against short-lived feature branches, and I don't want to have to set everything up by hand each time.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
也许不是预期的答案，但我的建议是换成另一个 CI 工具。例如，使用 Hudson 执行您所描述的操作将非常快速且简单（创建一个新的 maven2 项目构建，填写 scm url，然后就完成了）。
Maybe not the expected answer but my suggestion would be to change for another CI tool. Doing what you describe would be extremely fast and easy with Hudson for example (create a new maven2 project build, fill in the scm url and you're done).
如果这些短暂的功能分支不是那么重要，您可以将项目的 SCM Url 更改为您想要进行持续集成的新功能分支的 SCM Url。不幸的是，Continuum 不会在每个构建的构建历史记录中跟踪 SCM Url，但它更改 SCM Url 将提供您所需的内容，而无需每次都创建新项目。
If those short-lived feature branches are not that important, you could change the SCM Url for the project to the SCM Url of the new feature branch you want to do continuous integration upon. Unfortunately, Continuum does not track the SCM Url in the build history for each build, but it changing the SCM Url would provide what you need without creating a new project each time.