Use Case


Infrastructure Insight & Management
Powered by StackStorm

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.

Manual CI/CD Release Process Management

The Conventional Workflow Approach

Manual Process: 2-4 Stressful Hours for Network Operations (see Figure 1 below).

A user recognizes that a service has gone down and creates a ServiceNow ticket. Service Ops assigns the ticket to NetOps with a Priority 1.

NetOps team members now manually start diagnostics, discovering that an interface is down. Remediation action is performed to bring up the interface.

NetOps team now either updates the ticket if successful or continues running diagnostics to discover why the interface went down, staying as a priority level 1 task. The ServiceNow record is then updated and closed.

Figure 1 – Manual Interface Outage Response'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.
Maestro + Composer: 20-40 Stress Free Seconds (see Figure 2 below).

Automated CI/CD Release Process Management

Figure 2 – Maestro + Composer Automated Event Driven Network Remediation

Composer CI/CD Pipeline Automation

  1.  Everything starts when a developer checks in code, which could be via a merge or a pull request.
  2. That code check-in will be acknowledged by a Composer sensor at the integration layer of the code repository.
  3.  This acknowledgment of a code check in will send a trigger to Composer to start the testing stage.
  4. Composer will reserve a test bed and pull the Branch to the test bed.
  5. The test bed will then request the that was attached to the specified branch from the code repository.
  6. The branch will be fetched to the test bed.
  7. Upon successful preparation of the test bed a webhook will be kicked to Composer specifying the branch pull was a success.
  8. Composer will then tell a test server such as Jenkins to run predefined tests against the new branch in the test bed.
  9. The test server such as Jenkins will start the specified tests by installing the branch and running the tests.
  10. The CI testing will then initiate.
  11. 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.
  12. 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.
  13. The code repository such as GitHub will then move the branch to a package management tool such as Cloudsmith or PackageCloud.
  14. Finally, if the repository passes all dependency tests and build tests, then Composer will move the new branch to Production.

Composer Benefits

Higher quality code
Composer-automated CI/CD pipelines eliminate human errors and results in higher quality through a more efficient release process.

Faster release cycles
Eliminating manual intervention also results in dramatically faster release cycles as each pipeline stage completes the next initiates automatically.
Improved performance
Composer's event-driven architecture supports the entire CI/CD pipeline with real-time insight into performance or resource utilization issues.

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

Ready to see for yourself?

We'd love to show you how enables you to address a broad spectrum of orchestration & automation challenges.
Book a Demo