Hello, i'm quiet new in the CI/CCnet topic and looking for ideas or advice for automated versioning, packaging and deployment with ccnet.
I love the idea of lat ccnet the assembly version with the SvnRevisionLabeller or LatestchangeLabeller through the CCNetLabel property with the NAnt <asminfo> task. Is this a good practise? I heard from Ruben that this does not work well with WCF service/contract projects. What is your experience? Also i'm thinking about to automate the packaging and deployment process of creating zip files, click-once installers or msi setups. How do you do this in business? Currenty i'm using subversion and development takes place in /trunk/. If a new release is planned then /trunk/ is branched for example to: /branches/myApp-1.2/ and as soon as it is ready for deployment i tag it: /tags/myApp-1.2.0.0/ the development on head (trunk) goes on in the meantime. If later the version 1.2.0.0 required a bugfix then this is done in the "/branches/myApp-1.2/" branch and tagged again to "/tags/myApp-1.2.1.0/". Do you have for each release branch a ccnet project that generates a package/installer and tag the release? Or is there another solution for this? Otherwise i'll end up with really much projects in my webdashboard for every release branch. Thanks for your help and ideas. Best regards, Daniel
