Hudson设置版本控制的最佳实践(Best practices for versioning Hudson settings)

Hudson设置版本控制的最佳实践(Best practices for versioning Hudson settings)

我们经常在项目上使用Hudson持续集成服务器。 但是Hudson似乎缺乏适当的作业配置版本。

有几次，这导致了问题：有人改变或调整了作业上的配置以及过去工作的东西停止工作。

我试图在我的本地Hudson服务器（在我的笔记本电脑上）上进行版本控制作业。 但这不是最佳的：1）它只适合我。 2）我需要从中央构建服务器镜像作业 - 并且可能还需要修改它们以在本地工作。 3）为要忽略的文件设置.gitignores非常麻烦。

据我所知，哈德森没有办法查看工作的变化历史，也没有任何插件可以做到。

此外，似乎无法导出/导入设置。

所以问题是：你如何跟踪变化？ 在Hudson的工作和一般设置中都有？

We're using Hudson continuous integration server frequently on projects. But Hudson seems lacking of proper versioning of the jobs configuration.

A few times, this has lead to problems: Somebody changes or tweaks the configuration on jobs and something that used to work stopped working.

I have tried to version-control jobs on my local Hudson server (on my laptop). But this is not optimal: 1) it's only for me. 2) i need to mirror jobs from a central build server – and may also need to modify them to work locally. 3) It's pretty cumbersome to setup .gitignores for files to ignore.

As far as I know, there is no way in Hudson to view change history of jobs, and no plugin does it either.

Also, there seems to be no way to export/import settings.

So the question is: How do you keep track of changes? Both in jobs and in general setup of Hudson?

最满意答案

请参阅HUDSON_HOME的哪个部分应该置于源代码管理之下？

如果人们破坏配置并且您无法跟踪它，那么Audit Trail插件也可能对您有用。

See Which part of HUDSON_HOME should I put under source control?

The Audit Trail plugin might be useful to you too if people are breaking configurations and you're having trouble tracking it down.