Hi I'm looking for some suggestions on a good strategy to structure my projects in CCNet. I have 4 separate projects that all get built together every time a sourcetrigger detects a valid trigger. Setting them up as 4 separate CCNet projects allows me to track history of build performance for each one individually - even though all 4 always get built every time and could conceivably be setup as one single CCNet project with 4 compile tasks, one for each build
The question is - I want to have 3 separate "instances" of these 4 projects. One for continuous builds, one for nightly builds, and one (or more) for any temporary branches of these projects. 90% of the tasks in the CCNet projects would be the same in each instance - only paths and test tasks would differ (i.e nightly builds would run more tests than continuous builds) I tried setting up separate versions of each of these projects, using different names (e.g. ProjA.ContBuild, ProjA.NightlyBuild, ProjA.Branch, ProjB.ContBuild, etc...) with the different tasks for each project updated accordingly. The problem was this became too much of an administrative effort when needing to update the projects with any task modifications, and it crowded the dashboard display and became confusing to view I'm guessing this is pretty standard practice to have at least these 3 groupings (continuous, nightly, branches), so I'm curious how other people solved this issue with CCNet thanks Michael
