{"id":1794,"date":"2026-10-05T17:48:49","date_gmt":"2026-10-05T15:48:49","guid":{"rendered":"https:\/\/newsite.provalida.de\/?page_id=1794"},"modified":"2026-10-05T17:50:51","modified_gmt":"2026-10-05T15:50:51","slug":"deployment-automatisierung","status":"publish","type":"page","link":"https:\/\/www.provalida.de\/en\/software-devops\/deployment-automatisierung\/","title":{"rendered":"Deployment-Automatisierung"},"content":{"rendered":"
\n\t\t\t\t
\n \t\t\t
\n
\n
\n \t\t\t

Deployments without manual work<\/h1>\n\t\t\t\t\t

Less effort. Lower operating costs.<\/p>\n\t\t\t\t\t

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.<\/p>\n\t\t\t\t\t\n\tRequest the white paper\n<\/a>\n\t\t\n<\/div>\n\n<\/div>\n

\n
\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n\n<\/div>\n\n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n\n<\/section>\n\n\t\t\n<\/div>\n
\n
\n
\n \t\t\t

The challenge<\/p>\n\t\t\t\t\t

Every change has to arrive three times<\/h2>\n\t\t\t\t\t

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.<\/p>\n\t\t\n<\/div>\n

\n
\n \t\t\t

Knowledge in just a few heads<\/p>\n\t\t\t\t\t

Who transfers what, in which order, with which settings? With manual transport, quality depends on the individual.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

Version changes as a major effort<\/p>\n\t\t\t\t\t

Carrying over customisations, taking configurations into account, aligning system states: all over again with every change.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

Errors surface late<\/p>\n\t\t\t\t\t

If a change is missing, it is often only noticed in testing or in production. Then come corrections, retests and coordination.<\/p>\n\t\t\n<\/div>\n\n<\/div>\n\t\t\t

\u201cThe cost of a deployment rarely lies in the deployment itself, but in everything that has to be corrected afterwards.\u201d<\/p>\n\t\t\n<\/div>\n\n<\/section>\n

\n
\n
\n \t\t\t

The approach<\/p>\n\t\t\t\t\t

Understand the process first, then automate<\/h2>\n\t\t\t\t\t

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.<\/p>\n\t\t\n<\/div>\n

\n
\n \t\t\t

DEV<\/p>\n\t\t\t\t\t

Extension is developed<\/p>\n\t\t\n<\/div>\n\t\t\t

\u2192<\/p>\n\t\t

\n \t\t\t

TEST<\/p>\n\t\t\t\t\t

checked the same way<\/p>\n\t\t\n<\/div>\n\t\t\t

\u2192<\/p>\n\t\t

\n \t\t\t

PROD<\/p>\n\t\t\t\t\t

deployed to production reproducibly<\/p>\n\t\t\n<\/div>\n\n<\/div>\n

\n
\n \t\t\t

Reproducible deployments<\/p>\n\t\t\t\t\t

Consistent system states across all three environments, regardless of who is carrying out the deployment.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

A clear focus instead of a major project<\/p>\n\t\t\t\t\t

We start with the deployment operations within the platform, exactly where the effort repeats. The rest of your tool landscape stays as it is.<\/p>\n\t\t\n<\/div>\n\n<\/div>\n\t\t\t

\u201cNot automating everything, but automating the right things.\u201d<\/p>\n\t\t\n<\/div>\n\n<\/section>\n

\n
\n
\n \t\t\t

The benefit<\/p>\n\t\t\t\t\t

What you gain<\/h2>\n\t\t\n<\/div>\n
\n
\n \t\t\t

Lower operating costs<\/p>\n\t\t\t\t\t

Recurring steps run automatically. Experienced staff who previously looked after deployments gain time for further development and business requirements.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

Simpler quality assurance<\/p>\n\t\t\t\t\t

TEST and PROD are populated the same way. Tests check the functional quality of a change, not whether it has arrived in full.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

Better traceability<\/p>\n\t\t\t\t\t

You can see at any time which version has reached which environment. This helps with error analysis and with internal or external audit evidence.<\/p>\n\t\t\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n

\n
\n
\n \t\t\t

Your leverage<\/p>\n\t\t\t\t\t

What your savings depend on<\/h2>\n\t\t\t\t\t

As a rule of thumb: the more individual your system landscape and the more often you deploy, the greater the leverage.<\/p>\n\t\t\n<\/div>\n

\n
\n \t\t\t

01<\/p>\n\t\t\t\t\t

Number of environments<\/p>\n\t\t\t\t\t

With every additional environment, the effort for transport grows.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

02<\/p>\n\t\t\t\t\t

Scope of extensions<\/p>\n\t\t\t\t\t

The more custom adaptations, the more knowledge is tied up in the deployment.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t

03<\/p>\n\t\t\t\t\t

Frequency of deployments<\/p>\n\t\t\t\t\t

The benefit grows with every deployment that no longer has to be supervised manually.<\/p>\n\t\t\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n

\n
\n
\n
\n \t\t\t

In practice<\/p>\n\t\t\t\t\t

Already in use with customers<\/h2>\n\t\t\t\t\t

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.<\/p>\n\t\t\n<\/div>\n

\n \t\t\t\n\tDiscuss your deployment process\n<\/a>\n\t\t\t\t\t

\n\t\tMore on OpenText DevOps \u2192\n\t<\/a><\/p>\n\t\t\n<\/div>\n\n<\/div>\n\n<\/div>\n\n<\/section>\n

\n \t\t\t
\n
\n
\n
\n \t\t\t

White paper<\/p>\n\t\t\t\t\t

Deployments
without
manual work<\/h3>\n\t\t
\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n\n<\/div>\n
\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n
\n \n<\/div>\n\n<\/div>\n\n<\/div>\n
\n \n<\/div>\n\n<\/div>\n
\n \t\t\t

Free white paper<\/p>\n\t\t\t\t\t

Knowledge to
take away.<\/h2>\n\t\t\t\t\t

\u2713 Where manual effort arises in deployment
\u2713 How the transport from DEV via TEST to PROD can be automated
\u2713 What your savings depend on<\/p>\n\t\t\n<\/div>\n\n<\/div>\n

\n \t\t\t

Request the white paper<\/h3>\n\t\t
\n
\n \t\t\t