- More Labs
We use CruiseControl 2.7.1 to execute automatic builds. The build instance of CruiseControl is located at tampomud.iai.uni-bonn.de. Two build jobs are configured for Cultivate:
cultivate does our integration builds upon commited changesets. This job publishes the build result as cultivate.txt for the traffic light. The other job,
cultivate-release is used for release builds and publishes the generated update site. The working directory of CruiseControl is L:/Work/cc_build, both jobs have a appropriate subdirectory (cvt_34, cvt_34_release).
Current stable configuration is stored here and needs to be added to SVN, maybe have CruiseControl checkout his own configuration?
Cultivate uses the pluginbuilder Eclipse Plug-In to create automatic builds. The build files are contained in the CCCultivate project. All files in the project have been automatically generated by pluginbuilder. The main configuration of the builds is done in the graphical editor of the pluginbuilder.config file. We have defined two releases there:
Since automatically created build scripts did not work out of the box we changed the following files, a working version of those can be found in Revision 862:
After adding a new plug-in to a feature or adding a feature to pluginbuilder the build scripts have to be recreated by hitting the “Generate Build Files” link in the pluginbuilder.properties editor. This will not overwrite the changes made by us to the build scripts.
All details of plug-ins, features and update sites are described in a detailed manner in the following location:
Never mind, that you cannot see it with the browser. To check availability, you may try the site.xml.
There are currently two features in cultivate, but only the first one is included in the automatic build:
This feature contains the core parts of cultivate with the appropiate user interfaces. It consists of the following plug-ins:
This feature contains the refactor parts of cultivate, originated from a deploma thesis, including its dependencies. This feature currently is not tested amd needs more cleanups to run correctly.