How did this application deploy one year ago? How was the pipeline logic configured? What infrastructure model did it use? What application servers was it point to?

These questions all point to the same issue: enterprise application delivery is a changing business. New languages, new infrastructure, new platforms and services. Adapting the delivery process to satisfy every changing business or technology option requires careful change management strategies. Clarive helps deal with complex change by enabling careful configuration versioning.

Versioning is not something that needs to happen only at the source-code level. It needs to be taken seriously as organization-wide application delivery management issue. Every platform, every application parameters, every environment and infrastructure

Versioning In Clarive

Clarive implements several versioning mechanisms that allows for version control, with diff comparison, export/import, reuse and rollback features.

The two main versioning mechanisms in Clarive are:

• Instant Versioning: when saving a rule or CI, they are versioned by the system.
• Snapshots: manually (or automatically) triggered captures of environments, logic, configuration and/or templates.

You can use one or the other or both with Clarive. They are not mutually exclusive, and, in fact, it does not hurt to have separate strategies to using both of them at the same time.

Instant Versioning

Every time a user makes a change to a rule in Clarive that rule is saved as a version.

Versions can be tagged and compared. So you can compare the pipeline from a few days ago to the pipeline of a year ago if you wish. Rules can then be rolled back or copied.

But the main advantage of instant versioning is that, as we develop and work, we can rollback to a previous version.

Snapshots

Snapshots are the most complete and secure way to materialize the state of Clarive, be it current or already past.

Snapshots are a powerful configuration ……………………..

Advanced Versioning With Git

Now here’s the zenith of versioning delivery configuration: maintain a source-code repository, such as Git, with snapshot export files. And just commit the relevant changes.

This method then can be combined with Clarive changesets, releases, tests and deployment jobs to deliver changes in one instance of Clarive to other instances, creating a fully operational, enterprise-wide continuous delivery pipeline for your continuous delivery pipeline.

How about that for a change?