USE CASE
Manual CI/CD Release Process Management
Situation: CI/CD Pipeline With Manual Steps
-
Manual handling of code throughout its development lifecycle – Coding, QA/Test, Build, Deployment.
-
Lack of visibility throughout the release process lifecycle and manual test intervention risks extending time to deploy.
-
Releases process becomes stressful when excessive manual intervention introduces the risk of human error that forces unnecessary and costly rework and time delays.
-
A DevOps approach to release process management is challenged to achieve the true potential of CI/CD if significant manual intervention remains part of the process.
Orchestral.ai's Composer Solution
Composer provides out-of-the-box integration with hundreds of tools, apps devices and services used in DevOps and/or CI/CD pipeline environments. Composer provides an over-arching orchestration engine that integrates and automates the entire end-to-end CI/CD pipeline without the need to "rip and replace". Composer's event-driven architecture ensures the appropriate actions, notifications and alerts are triggered in real-time for fluid, reliable and efficient CI/CD release process management.
Automated CI/CD Release Process Management
Composer CI/CD Pipeline Automation
-
Everything starts when a developer checks in code, which could be via a merge or a pull request.
-
That code check-in will be acknowledged by a Composer sensor at the integration layer of the code repository.
-
This acknowledgment of a code check in will send a trigger to Composer to start the testing stage.
-
Composer will reserve a test bed and pull the Branch to the test bed.
-
The test bed will then request the that was attached to the specified branch from the code repository.
-
The branch will be fetched to the test bed.
-
Upon successful preparation of the test bed a webhook will be kicked to Composer specifying the branch pull was a success.
-
Composer will then tell a test server such as Jenkins to run predefined tests against the new branch in the test bed.
-
The test server such as Jenkins will start the specified tests by installing the branch and running the tests.
-
The CI testing will then initiate.
-
Whether successful or not, Composer will trigger an email to the developer team to ensure they are aware of the status and progress of the code.
-
If successful, Composer will then start the build process and tell the code repository to move the branch to the next stage whether that be pre-production or production.
-
The code repository such as GitHub will then move the branch to a package management tool such as Cloudsmith or PackageCloud.
-
Finally, if the repository passes all dependency tests and build tests, then Composer will move the new branch to Production.
Composer-automated CI/CD pipelines eliminate human errors and results in higher quality through a more efficient release process.
Higher quality code
Eliminating manual intervention also results in dramatically faster release cycles as each pipeline stage completes the next initiates automatically.
Faster release cycles
Composer's event-driven architecture supports the entire CI/CD pipeline with real-time insight into performance or resource utilization issues.
Improved performance
Composer Benefits
Getting Started
Orchestral's solutions are available as free 30-day Proof of Value evaluations. To get started, just click the "FREE TRIAL" button at the top of this page and complete the Trial Request Form. If you'd like to see a demo first, just click the "Book a Demo" button below to book a date/time that works best for you. Otherwise, you can get started by emailing us at info@orchestral.ai.