The following table defines configurable options in CloudBees Release Orchestration SaaS, and lists the corresponding links to more information.
| Name and link | Definition |
|---|---|
Source control management (SCM) is a tool allowing multiple developers to work simultaneously, committing and merging code without conflicts. |
|
Continuous integration (CI) is a DevOps software development practice that allows developers to check their code into shared repositories. |
|
An environment is a collection of resources, such as Kubernetes clusters and virtual machines, to deploy your pipelines. |
|
Test management is essential in a software delivery process to ensure fewer errors in code and design, and to improve the quality of a product. |
|
CloudBees Release Orchestration SaaS provides a view of all bugs and issues related to the deployment of new feature development. |
|
Continuous deployment(CD) is designed to increase the release velocity while reducing the risk associated with updating applications. |
|
The build repository is a tool to store the binary of the build. CloudBees Release Orchestration SaaS supports JFrog and AWS ECR repositories. |
|
Observability helps measure the internal states of a system by examining its outputs. |
|
CloudBees Release Orchestration SaaS integrates with Jira, so that the pipeline status can be updated in Jira. |
|
Settings-as-code (SasC) is a practice of maintaining all settings in files in a repository. |