CI/CD standard

Solve your problems or get new ideas with basic brainstorming

Get Started. It's Free
or sign up with your email address
Rocket clouds
CI/CD standard by Mind Map: CI/CD standard

1. Goals

1.1. Increase project velocity

1.2. Increase project qualiity

1.3. Decrease manual efforts

1.4. Increase our service offerings

1.5. Enforce accountability

1.6. Standarized Project workflow

1.7. Reduced risk during final deployment

2. Problems

2.1. Culture shift might not be fully accepted

2.2. Drowning in tools

2.3. Data Volume changes performance between environments

2.4. Performance Testing

3. Ideas

3.1. Identify a tool/company we can partner with

3.1.1. Docker?

3.1.2. Jenkins

3.1.3. Gerrit

3.2. Train subject matter experts

3.3. Move to component centered delivery

3.4. automate, automate, automate

3.5. build it

4. Questions

4.1. Do we have the expertise?

4.2. Do we have the right support in place?

5. Current - Documented

5.1. Role

5.1.1. Technical Lead

5.1.1.1. Create Continuous Integration Plan

5.1.1.2. Deployment Walkthrough With Client

5.1.1.3. Create Release Notes

5.1.2. Deployment Engineer

5.1.2.1. Deployment Planning

5.1.2.2. Product Packaging

5.1.2.3. Product Delivery

5.1.2.4. Product Deployment

5.1.3. Client

5.1.3.1. Deployment Validation

5.2. Toolset

6. New Standard

6.1. Testing

6.1.1. Automated

6.1.2. Test Driven Development

6.1.3. Peformance

6.2. Deployment Pipeline

6.2.1. Enviroments

6.2.1.1. Dev

6.2.1.2. QA

6.2.1.3. Staging

6.2.1.4. Production

6.2.2. Config Defined by Enviroemnt

6.3. Source Control

7. Workflow

7.1. Source Control

7.1.1. Sprint Branch

7.1.1.1. Create story branch

7.1.1.2. Code/Peer Review

7.1.2. Unit / Functional Test

7.1.3. Merge

7.2. Testing

7.2.1. Automate tests

7.2.2. Test Driven Development

7.2.3. Integration tests

7.3. Deployment Pipeline

7.3.1. One build for all enviroments

7.3.2. Automated releases

8. AGI Model

8.1. Development

8.1.1. Sprint Branches

8.1.1.1. Story/Task/Bug Fix Branch within Sprint Branch

8.1.1.2. merging

8.1.1.2.1. Merge Sprint Branch Into Story/Task/Bug Fix Branch After development is complete

8.1.1.2.2. Merge changes into sprint branch if all unit tests have been passed

8.1.1.3. Pull Requests

8.1.2. Reviews

8.1.2.1. Demo

8.1.2.2. Code/Peer Review

8.1.3. Sprint Closing

8.2. Source Control

8.2.1. Technology

8.2.1.1. Git

8.3. Environments

8.3.1. CI Server Environment running current Sprint

8.4. Testing

8.4.1. Unit Tests

8.4.1.1. technologies

8.4.1.1.1. JUnit

8.4.1.1.2. Spock

8.4.1.2. Owners

8.4.1.2.1. Developer

8.4.2. Functional Testing

8.4.2.1. Technologies

8.4.2.1.1. Geb

8.4.2.2. Owners

8.4.2.2.1. QA

8.4.2.2.2. Developer

8.5. Verification and Acceptance on CI Server

9. DevOps Application Lifecycle Management (ALM)

9.1. Planning

9.1.1. Sprint Planning

9.1.2. Agile Board Utilization

9.1.3. Task Management

9.1.4. Charting & Dashboards

9.2. Develop + Test

9.2.1. Version Control

9.2.1.1. Branching Strategy

9.2.1.1.1. TFVC

9.2.1.1.2. Git

9.2.1.1.3. Subversion

9.2.2. Testing

9.2.2.1. Unit Testing

9.2.2.1.1. JUnit

9.2.2.1.2. NUnit

9.2.2.1.3. TestNG

9.2.2.2. Performance Testing

9.2.2.2.1. JMeter

9.2.2.3. Web Testing

9.2.2.3.1. Selenium

9.2.2.3.2. Spock

9.2.2.3.3. Geb

9.2.3. Code Analysis

9.2.3.1. Checkstyle

9.2.3.1.1. Checkstyle Rule Definitions

9.2.3.1.2. IDE Plugin

9.2.3.2. Cobetrua

9.2.3.3. SonarQube

9.2.4. Build Tools

9.2.4.1. Apache Maven

9.2.4.2. Gradle

9.2.4.3. Ant

9.2.4.4. MSBuild

9.3. Release

9.3.1. Continuous Integration

9.3.1.1. Jenkins

9.3.1.1.1. Jenkins Job Builder

9.3.1.1.2. Jenkins Pipeline Plugin

9.3.1.1.3. Maven Release Plugin

9.3.1.2. Fabric8

9.3.1.3. OpsWorks

9.3.1.4. Visual Studio Team Services

9.3.2. Continuous Delivery

9.3.2.1. Release Workflow

9.3.2.2. Configuration As Code

9.3.2.3. Container Virtualization

9.4. Monitor

9.4.1. Application Health

9.4.1.1. Availability Metrics

9.4.1.2. Performance Metrics

9.4.1.3. System Metrics

9.4.1.4. Alerts