Difference between revisions of "Release Management and Automating Deployment"
From CitconWiki
Jump to navigationJump to searchSadovnikov (talk | contribs) (New page: * Customers are not CI servers - they need to be ready for an update * Regular deployments to any of the environments (including production), even if there are no updates, work like CI ser...) |
|||
| Line 1: | Line 1: | ||
* Customers are not CI servers - they need to be ready for an update | * Customers are not CI servers - they need to be ready for an update | ||
* Regular deployments to any of the environments (including production), even if there are no updates, work like CI servers for developers - problems with deployment are exposed early. Failed deployment does not hurt, if there is a good roll-back procedure | * Regular deployments to any of the environments (including production), even if there are no updates, work like CI servers for developers - problems with deployment are exposed early. Failed deployment does not hurt, if there is a good roll-back procedure | ||
| + | * [http://www.bitwalker.nl/blog/automatic-application-deployment-with-maven-and-luntbuild Automatic application deployment with Maven and Luntbuild] | ||
Latest revision as of 13:11, 1 November 2008
- Customers are not CI servers - they need to be ready for an update
- Regular deployments to any of the environments (including production), even if there are no updates, work like CI servers for developers - problems with deployment are exposed early. Failed deployment does not hurt, if there is a good roll-back procedure
- Automatic application deployment with Maven and Luntbuild
