-
Notifications
You must be signed in to change notification settings - Fork 0
ContinuousBuild
The purpose of the continuous build is to have deployable artifacts (products and update sites) that reflect the current state of the repository.
Right now, we are re-using the Hudson server set up for IRMIS at [https://irmis-dev.bnl.gov/jenkins]. A job is setup to build the nsls2 product at every change within the repository. Other jobs can be setup for each different product. The final tarball are archived and published by Hudson.
Another job in hudson copies the update site generated by the build to the sourceforge web space. The convention is http://cs-studio.sourceforge.net/[[. For the nsls2 product, for example, http://cs-studio.sourceforge.net/nsls2/dev-updates/ . This update site is intended for developers, or power users, and it leaves the possibility of hosting a production update site at http://cs-studio.sourceforge.net/[product|product]/dev-updates/]]/updates/ . Once a version is finalized, to promote the build one can simply copy the final update site to the desired location.