continuous integration - Publish a specific revision using CruiseControl.Net -
i setting cruisecontrol.net server. far, builds project (.net website), , kind-of know how set unit testing, code coverage, etc in future.
what need have this:
the developers commit changes svn continually, ccnet builds often. ccnet publish latest version development server, commit validated (with unit tests etc). the project manager validates specific version, in order publish pre-production server, , create svn tag revision.the lastly point problem lies: how can set things project manager can, instance, browse ccnet web dashboard, select previous specific build, , says "this build want publish" ?
i believe thinking flawed somewhere, can't set finger on it. maybe ccnet not right place these manipulations ?
in mind, can create svn tag using ccnet, , work trunk, maybe can't ? maybe it's other way around, , should add together ccnet project every time tag created under svn ?
the final goal want automate publication process: zip creation (for archiving), web.config modification (using nant instance), , website publication (using ftp). in these steps, want limit manual intervention maximum. if can avoid add together new project ccnet every time tag or branch created in svn, awesome.
thanks help, , sorry if it's not easy read, it's not clear in head either...
since can create task, should able accomplish goal, though unfortunately not out-of-the-box.
since utilize svn, depends on revision. think i'd create separate project 3rd scenario , added parameter pm provide revision number. based on i'd tag sources etc. in own task.
regarding other points, think similar. web projects started using msdeploy, , in each stage build msdeploy bundle created. there separate build called deploy, when forced allows select bundle want deploy using msdeploy.
having several environments, however, started little bit overkill managing ccnet, , i'll looking kwakee @ time.
continuous-integration cruisecontrol.net publishing
No comments:
Post a Comment