You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
This document provide the definition of the roles for this project. It also has a list of tools used for the CI/CD.
Roles
| Role | Responsibilities | Who |
|---|
| Release Manager | - Oversee the coordination, integration, and flow of development, testing, and deployment to support continuous delivery.
- Work closely with Product Owner and Project Manager to create product release road maps, release plans, identify dependencies, and communication flows between stakeholders.
| <<Name of the Person who is assigned>> |
Testers / Quality Assurance Engineers | Find out desired test types to validate the quality of the product. Work with Developers and Project Managers to determine test implementation and methodology, as well as tools required to operate the testing. Write test cases, prioritize and categorize the difficulty level of the test cases. Create documentation of the test cases to make sure the test cases are understood by the rest of the team.
| <<Name of the Person who is assigned>> |
| Developers | - Transform business goals of users (as customer) to software/system.
- To be the owner of end-to-end engineering life-cycle of the solution from requirement analysis, architectural vision, testing, UX, extensibility, operations, maintenance, and end-of-life.
- Ensure the continuous delivery of the solution to your users/customers to create rapid and uninterrupted value for the business.
| <<Name of the Person who is assigned>> |
| Category | Tools | Remarks |
|---|
| Continuous Delivery Pipeline Tools |
| Example: Jenkins, Bitbucket Pipeline, Travis CI, etc |
| Coding/Build Tools |
| Example: VM, or Docker image |
| Review/Testing Tools |
| Example: FishEye, Cucumber, JUnit, JMeter, Selenium, etc |
| Monitoring Tools |
| Example: Nagios, Zabbix, etc |
| Issue Tracking Tools |
| Example: JIRA, Asana, etc |
Release Process
For Git based repository,
- release is triggered by Pull Request by developer.
- Once approved and merged to destined repository, pipeline will handle the build and deployment based on the environment.
- For production release, it should be based on tag version.
- Once tag is created in origin, pipeline should handle the build and deployment.
Release Flow Diagram
<<To be added with a diagram to explain the flow of the release>>
