|
Tasks for CLCS
CLCS is designed to address many common situations that software organizations encounter. CLCS helps perform these tasks via a command line interface, using direct commands or a script file
Extract a baseline version –
- Some shops want the developers to work with a common set of files that are updated daily or on a schedule. That "baseline" may be the most current Development version of all the files. The developer
overlays that set with his versions of the specific files he/she is changing.
In this way, each developer is constantly "integrating their changes with those made by others. Using a CLCS script, it is straightforward to extract the baseline versions.
Promote a version from one environment to another –
- A customer may have several environments that its software functions in: a development area, an integration testing area, preproduction test and production areas. Each environment may have different database
files in different locations and other "environmental" variables.
As a software release moves from one environment to another, it may have to be rebuilt with different compilers, even on a different operating system version. The versions produced may be the same, but the targets and the build tools and actions may be different.
Distribute to multiple nodes –
- After the software is ready for production use, it may be necessary to copy the "package" to staging areas on other nodes at the proper time. The distributed items might be object files, source files or a
mix. The application may involve several 'tiers' with different platforms and software on each tier.
|
