Less effort. Lower operating costs.
Custom extensions in OpenText Software Delivery Management (formerly ALM Octane) move automatically from DEV via TEST to PROD. An approach from our own practice, already successfully implemented for customers.
Request the white paperThe challenge
Hardly any company uses its software delivery platform out of the box. Applications, integrations and extensions adapt the system to the company's own processes. That is exactly what makes the platform valuable. In day-to-day operations, however, it creates a process that is often underestimated: transporting these customisations through all environments.
Knowledge in just a few heads
Who transfers what, in which order, with which settings? With manual transport, quality depends on the individual.
Version changes as a major effort
Carrying over customisations, taking configurations into account, aligning system states: all over again with every change.
Errors surface late
If a change is missing, it is often only noticed in testing or in production. Then come corrections, retests and coordination.
“The cost of a deployment rarely lies in the deployment itself, but in everything that has to be corrected afterwards.”
The approach
We analyse which steps are involved in transport between environments, where they repeat and where errors occur. The result is a standardised process: what was developed in DEV and checked in TEST reaches PROD by the same route.
DEV
Extension is developed
→
TEST
checked the same way
→
PROD
deployed to production reproducibly
Reproducible deployments
Consistent system states across all three environments, regardless of who is carrying out the deployment.
A clear focus instead of a major project
We start with the deployment operations within the platform, exactly where the effort repeats. The rest of your tool landscape stays as it is.
“Not automating everything, but automating the right things.”
The benefit
Lower operating costs
Recurring steps run automatically. Experienced staff who previously looked after deployments gain time for further development and business requirements.
Simpler quality assurance
TEST and PROD are populated the same way. Tests check the functional quality of a change, not whether it has arrived in full.
Better traceability
You can see at any time which version has reached which environment. This helps with error analysis and with internal or external audit evidence.
Your leverage
As a rule of thumb: the more individual your system landscape and the more often you deploy, the greater the leverage.
01
Number of environments
With every additional environment, the effort for transport grows.
02
Scope of extensions
The more custom adaptations, the more knowledge is tied up in the deployment.
03
Frequency of deployments
The benefit grows with every deployment that no longer has to be supervised manually.
In practice
In customer projects with OpenText Software Delivery Management, we have automated the transport of custom extensions across all environments. In an initial conversation, we will assess together where the greatest leverage lies in your landscape.
White paper
Free white paper
✓ Where manual effort arises in deployment
✓ How the transport from DEV via TEST to PROD can be automated
✓ What your savings depend on
Would you like to reduce the manual effort of transporting customisations between your environments? Tell us about your current situation. Together we will look at which steps can be automated and what savings are realistic.
Write to us
Prefer to talk directly?
Choose an available slot directly in our calendar, free of charge and without obligation. We will discuss your requirements and show you possible solutions.
Choose an appointment