All depends on how you do this deployment, is it only file copy or is it through a installer (is installer able to correctly install over an existing installation)?
Doing something similar about a year ago for a production we just did a copy into a network share before stopping the IIS on the remote server (you can just go and stop the Web Application, there are some tasks that allow control or IIS). But this was a QA server. Using an installer could be done through be done at least through psexec. Hope it helps, florin On 17 feb., 23:49, Jeff <[email protected]> wrote: > Hello! > > I want to make cc.net the vehicle for deploying the web sites that my > group works on. That means that cc.net will need to push files to a > development server, QA server and a production server. cc.net will > need to be able to discriminate between the different targets ideally > by some sort of user input on the dashboard. For instance, the > continuous integration build deploys to the dev server, but the > dashboard also would have a [Deploy to Staging] button and a [Deploy > to Production] button. Or something else to that point. > > I found a blog series where Trey Hucheson talks about how to build > cc.net addons to do exactly this but his info is almost 2 years old > and he was working against cc.net version 1.2. So, I am hesitant to > recreate his work. > > Is it possible to accomplish my requirements above? How hard would it > be to implement? If anyone is familiar with Trey's work, do you know > if it would still work with cc.net v1.4? > > Thanks! Jeff
