Release process

Get Started. It's Free
or sign up with your email address
Rocket clouds
Release process by Mind Map: Release process

1. Releases

1.1. Make all releases automatically on TeamCity

1.1.1. Triggers

1.1.1.1. Each night if some changes in some specific branch (master or release)

1.1.1.2. By push to some specific blanch

1.1.2. BE

1.1.2.1. Use release plugin

1.1.2.2. Move ucimp-install-sources on the same level

1.1.3. FE

1.1.3.1. Need clarification from Filip

1.2. Store released artifacts

1.2.1. SharePoint as now

1.2.2. Release management system

2. Meta release (make automatically on each BE/FE release new meta release)

2.1. Team City

2.2. Octopus

3. Release management

3.1. Octopus Deploy

3.1.1. Storage: Octopus

3.1.2. Management: email with possible automation in Octopus

3.1.3. Test status: Octopus with email notification

3.1.4. Which versions on which environments - Octopus

3.1.5. Deploy: Octopus

3.1.6. Required access to Octopus only*

3.2. Current (manual)

3.2.1. Storage: SharePoint

3.2.2. Management: email

3.2.3. Test status: email

3.2.4. Which versions on which environments - on Confluence page (manual)

3.2.5. Deploy: manual

3.2.6. Required access to each resource (email, confluence, sharepoint, database and all deployment nodes)

4. Estimated work

4.1. Automatically builds

4.1.1. BE: 2-3 MD

4.1.2. FE: 2-3 MD

4.2. Deploy improvements 1 MD

4.3. Octopus

4.3.1. POC - 3 MD

4.3.2. Setup for all environments: 3-5 MD

4.4. Meta-release: 2 MD

4.5. Migration to GitLab 2-3 MD

4.6. Team Citi update 1 MD

4.7. Coordination/ Analysis / Meetings 5 MD

5. Deploy

5.1. Initial deploy: manual

5.2. Continues deploy: automatically

5.2.1. tunnel to production

5.2.2. deploy on each node

5.2.3. run incremental DB scripts

6. Resources

6.1. Team Citi

6.1.1. Update to the actual version

6.1.2. Build agent licence 8,193.00 Kč (not necessary now)

6.2. GitLab

6.2.1. Use existing TRASK instance

6.3. Octopus

6.3.1. Install

6.3.1.1. Existing win server

6.3.1.2. MS SQL

6.3.1.2.1. Existing TRASK MS SQL

6.3.1.2.2. Local Express MS SQL

6.3.2. License

6.3.2.1. Free - allows you to deploy up to 5 projects to up to 10 target machines, and is limited to 5 users

6.3.2.2. Professional ($ 700.00 USD) - 20 users, 20 projects and 20 target machines.

7. Steps

7.1. Move the release from local PC to TeamCity for BE

7.2. Move the release from local PC to TeamCity for FE

7.3. POC of Octopus

7.4. Simplify the deployment (do the tomcat deploy and DB update) by single command

7.5. Automatically trigger release procces

7.6. Use Octopus to promote (deploy) releases to target environments

7.7. Automatically create meta-release