On Nov 26, 2009, at 9:31 AM, Mark Phippard wrote: > On Thu, Nov 26, 2009 at 10:27 AM, Hyrum K. Wright > <[email protected]> wrote: >> >> On Nov 25, 2009, at 11:36 PM, Bhuvaneswaran A wrote: >> >>> As discussed in this email thread [1], please find attached the patch to >>> add Hudson jobs in the repository. This patch adds the Hudson >>> configuration files in build/hudson/ directory. These jobs are already >>> setup and tested in the build farm. The Solaris specific jobs can be >>> added later, after they are verified. >>> >>> [[ >>> The configuration files for Hudson jobs added in Apache build farm. >>> >>> * build/hudson/README >>> Document the configuration of Hudson jobs. >>> >>> * build/hudson/jobs/subversion-trunk-ubuntu/config.xml >>> The configuration file specific to building Subversion in trunk on >>> Ubuntu system. >>> >>> * build/hudson/jobs/subversion-1.6.x-ubuntu/config.xml >>> The configuration file specific to building Subversion in "1.6.x" >>> branch on Ubuntu system. >> >> Shouldn't this go on the 1.6.x branch? > > No. This is just storing the configuration files for the Hudson > build. It is nothing specific to the release. We do not backport the > buildbot configuration to the release branches. > > Hudson is just configured differently in that there would be a > different job for each path we want to build. It will only build the > 1.6.x branch when it sees something committed. > > IMO, it would make sense to only store and track these in trunk.
I've only played around with Hudson a little, so I'm not too familiar with it. At some point, we'll branch trunk to 1.7.x, and the release branch will have the configuration file in it. At that point, is the configuration static, or do we expect to change configurations for release branches frequently? Or would we have to change it anyway, since the config file contents would still think they pertain to trunk? -Hyrum
