Continuum Tip: Builds Scheduling
"When scheduling project builds in Continuum, keep development builds and nightly builds separate. Development builds should run quick and often so that broken builds are immediately flagged, while nightly builds should run everything and must deploy the generated artifacts to an accessible repository where developers and QA members can retrieve it the following day."
For example, if most of the development work happens during daytime, you can schedule your development builds to run every two or three hours (depending on how long your builds take) during the day when changes are being pushed in your source repository. You can simply configure it with "clean install" as you goals since the purpose of the development builds is to ensure that your build is not broken.
On the other hand, you can schedule your nightly builds to run at night (say every 10 in the evening). All the integration tests must be executed and builds must be deployed to your internal artifact
repository. This ensures that the development team and the QA team get all the changes from the previous day when they build the project and test the nightly builds the following day, respectively.
Make sure that your build notifications are configured so that the development team are immediately notified if the build breaks.
SPEAK / ADD YOUR COMMENT
Comments are moderated.
