I generally tag before a build, then pull the tag, and build/test it. We use a combination of project name plus timestamp for daily/test builds. This seems to be a pretty widely-used practice.
Then if we decide to go RC or full release for a given tag, we can either retag it with a more descriptive tag ie project_1.0.0_RC1 or project_1.0.0_final or just keep track of the original tag in release notes somewhere. As for copying the complete working directory, sounds like something you will need to build yourself and add to Continuum if you can't find it already implemented in the product. Wayne On 3/30/06, Gautham Pamu <[EMAIL PROTECTED]> wrote: > maven install and deploy uploads the jars,poms to the local/remote > repository but I want the copy the complete working directory > files sourcecode etc to the shared file system. > > I also want to tag the module before starting the build, is it possible to > tag using continuum or maven goal > > >In order to name the current end of the main trunk of a module, use the > command > > >cvs rtag *Tagname my_module* > > I have another question, whats it the best practice for tag the code, is it > after build or before build and whats the convention followed for tag names. > > Thanks > Gautham Pamu > > On 3/30/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > I don't use Continuum at this point, but can't you run a "mvn install" > > or "mvn deploy" kind of command after the build successfully builds, > > which will install/deploy your build to a specified location? > > > > Wayne > > > > > > On 3/30/06, Gautham Pamu <[EMAIL PROTECTED]> wrote: > > > Hi Everyone, > > > > > > I am using Maven 1.0.2 and Continuum 1.0.2, I want to copy the complete > > > build to a shared file system. Whats the best way to acheive it, > > > are they are plugins in maven or configuration in continuum to copy the > > > build to shared file system. > > > > > > -- > > > -Gautham Pamu > > > > > > > > > > > > -- > -Gautham Pamu > >
