Skip to main content

Start developing

After the initial provisioning, you can start developing your InsuranceSuite applications. Their basic versions are already deployed to a non-production development planet of the Dev class.

Build and dockerize

All the work with InsuranceSuite applications begins in Atlassian Bitbucket. The Bitbucket project, to which you get access at initial provisioning, contains repositories with your InsuranceSuite applications. You can clone the repositories and introduce changes using Git version control system.

A diagram with first steps with Cloud Platform.

Deploy to development planets

After you commit your changes to the feature branch of a repository, the new builds are automatically tested and dockerized in TeamCity. The builds for Docker images of your applications become available on the dev planet for deployment. You can deploy the new builds to a development planet.

A diagram with workflow for building and dockerizing in Cloud Platform.

Test

For further testing, you can deploy the builds to other non-production planets of the following classes:

  • QA for quality assurance process.
  • UAT for user acceptance testing.

Promote and deploy to pre-production and production

You can promote your builds to a pre-production planet for further testing. You can deploy the InsuranceSuite Docker images to the planet of a PreProd class for testing with production data.

On pre-production planets, you can test your builds with the production data. The production database backup is available for restore on the dryrun pre-production planet automatically. When you've tested your builds in pre-production, you can promote them to a production planet. You can perform self-service deployments to a production planet.

A diagram with workflow for promoting to pre-production and production planets.

See also

  1. Bitbucket
  2. Build and dockerize
  3. Deploy InsuranceSuite applications
  4. Promote builds between star systems
  5. Test InsuranceSuite applications