Skip to end of metadata
Go to start of metadata

Automatically deploy the latest changes.

Continuous Deployment

A process that detects new releases into your software repo. Essentially, each time this process detects a new artifact, it will attempt to deploy it to a specified environment. Typically, this is applied in organizations where users want to test functionality as soon as possible. Example:

  1. You commit your code
  2. The Nightly Build deploys a artifact/application file into your repository
  3. The Continuous Deployment process detects the new application and copies it into a deployment folder (see for example How to deploy to IBM WebSphere 6.x)
  4. The process executes a routine that instruments a test server into undeploying the previous version installing the new application and booting it up
  5. The process also triggers integration tests that verifies that the server is running correctly afterwards.

See also Continuous deployment in 5 easy steps , Why Continuous Deployment?

Full Size
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.