HUDSON_HOME的哪个部分应该放在源代码管理下？ [英] Which part of HUDSON_HOME should I put under source control?

问题描述

我想使用subversion管理Hudson的配置文件进行备份。
Hudson Wiki 列出了$ HUDSON_HOME的目录结构像这样：

  HUDSON_HOME 
 +  -  config.xml（hudson根配置）
 +  -  *。 xml（其他站点配置文件）
 +  - 指纹（存储指纹记录）
 +  - 插件（存储插件）
 +  -  jobs 
 +  -  [JOBNAME] 
 +  -  config.xml（作业配置文件）
 +  - 工作区（版本控制系统的工作目录）
 +  -  latest（最后一个成功构建的符号链接） ）
 +  -  builds 
 +  -  [BUILD_ID]（对于每个构建）
 +  -  build.xml（构建结果摘要）
 +  -  log（日志文件）
 +  -  changelog.xml（更改日志）
  

显然，作业/ [JOBNAME] / builds不应进入源代码控制，但config.xml是一个很好的候选人。

解决方案

如何管理您的Hudson配置？ div>

我使用SCM来管理我的Hudson配置。我保持每个作业的顶级config.xml和config.xml。我有一个小的脚本，我用来从Hudson获取配置，并根据需要提交/添加/删除它们（以及一些其他的响铃和口哨，使管理配置更容易）。

Re Rob Hruska的点数，对于我的特定设置：

• 配置经常更改>
  
• （请参阅上面的脚本进行更新）


• 我会一直处理。我们有多个管理员可以更新配置，这些差异是有用的

总之，每种情况都不同。我做的配置管理没有（而不是）免费。一个cron作业，每晚拉链一切，肯定是更便宜，也可能是足够的。

I'd like to manage Hudson's configuration files with subversion for backup. The Hudson Wiki lists the directory structure of $HUDSON_HOME like so:

HUDSON_HOME
 +- config.xml     (hudson root configuration)
 +- *.xml          (other site-wide configuration files)
 +- fingerprints   (stores fingerprint records)
 +- plugins        (stores plugins)
 +- jobs
     +- [JOBNAME]      (sub directory for each job)
         +- config.xml     (job configuration file)
         +- workspace      (working directory for the version control system)
         +- latest         (symbolic link to the last successful build)
         +- builds
             +- [BUILD_ID]     (for each build)
                 +- build.xml      (build result summary)
                 +- log            (log file)
                 +- changelog.xml  (change log)

Obviously jobs/[JOBNAME]/builds shouldn't go into source control but config.xml is a good candidate. Plugins and fingerprints are less obvious.

How do you manage your Hudson configurations?

解决方案

I do use an SCM for managing my Hudson configuration. I keep the top-level config.xml and the config.xml for each job. I've got a little script that I use to fetch the configs from Hudson and commit/add/delete them as necessary (along with some other bells and whistles that makes managing the configuration easier).

Re Rob Hruska's points, for my particular setup:

• configurations do change often (notifications, especially)
• (see above re a script to make the updates)
• I diff things all the time. We have more than one admin who can update the configuration, and these diffs are useful

All that said, every situation is different. The management I do for the configs didn't (and doesn't) come for free. A cron job that zips everything up nightly is definitely cheaper and may be sufficient, too.

这篇关于HUDSON_HOME的哪个部分应该放在源代码管理下？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！