Wim, it looks good to me from base SCM configuration perspective.
I use a mixture of UCM and base SCM configurations. I keep the configspec file
in base SCM. At the time doing the label, I update the confispec file and label that
config spec only.
At the perform step, i then create a view and load that configspec file base the label
and the rest is the same as yours.
so our maven-scm's checkout and label command will be different. But we both use a
config spec file during checkout.
Emmanuel, how would we go about implementing these commands?
I will be out to town with limited access to internet. Will discuss more when I get back.
-D
On 11/23/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
Hi,
to make release:perform work on ClearCase we need to implement the 'checkout' command for ClearCase (this is not what ClearCase user would call checkout!). As I understand it, 'checkout' should copy the files (with a certain tag) from the source control system to a certain directory and then the build should start on those files. So this is what we need for ClearCase:
- create a view with a config spec: Since we need to look at a released version and it has been labeled in release:prepare if all is ok, we only need 1 line in the config spec, like this
ELEMENT * RLS_MYPROJECT_V1.0
- mount the correct vob. Don't know if this is really necessairy, the correct vob should normally already be mounted
- cd to the created view
- copy everything to a directory (or run the build from the newly created view?)
This is the commando's I think we will need to call:
// First create the view
cleartool mkview -tag maven_release_build_view \\MYCOMPUTER\cc_vws1\maven_release_build_view.vws
// Assign the correct config spec
[Create a temp file called configspec.txt with the config spec in it]
cleartool setcs -tag maven_release_build_view configspec.txt
[Following 2 lines maybe better left out for now]
cleartool umount -all
cleartool mount \my_own_vob
//Do the build here
//Call the following line after the build - If this is not possible to call after the build, run it at the start of the next build
cleartool rmview -force -tag maven_release_build_view
anybody who agrees or disagrees, please comment!
regards,
Wim
