3C Release Manager for Automic

The 3C Release Manager moves Automic Automation objects between DEV, TEST, UAT and PROD in a controlled way – based on snapshots, diffs and deployment packages. Every deployment is backed up, validated and logged, so you always know what moved and how to roll it back.

Compatible with

Automic Automation V21/V24/V26

Deployment

SaaS or on-premise

Licence

Subscription, 1–3 years

Support

Included for the full term

Price

On Request

Overview

The 3C Release Manager is Tricise’s release governance solution for Automic Automation. It captures the configuration of your Automic environments as snapshots, shows the differences between environments or points in time, and bundles the changes you select into deployment packages – turning ad-hoc transports into auditable, repeatable releases.

Before each deployment, the 3C Release Manager creates a backup snapshot, and afterwards a validation snapshot. If something goes wrong, the Rollback button generates a reverse deployment that restores the previous state. Changes are grouped into user stories, conflicts between parallel stories are flagged before they reach production, and the audit log records every important action with user and timestamp.

Features

Snapshots & diffs:
  • Incremental snapshots of your Automic configuration
  • Scheduled snapshots with automatic diffs
  • Compare two snapshots or two environments
  • XML and tree view for every object
Deployments & rollback:
  • Deployment packages from snapshots, diffs or user stories
  • Recursive transports with deep scan
  • Backup and validation snapshot for every deployment
  • Rollback as a reverse deployment
Governance & teamwork:
  • User stories, linkable to ticket systems such as Jira
  • Conflict analysis for parallel teams
  • Role-based access with custom roles
  • Optional four-eyes principle and audit log
Mass changes & Git:
  • Rule-based mass changes during deployment
  • Same syntax as the Automic AEDB Change utility
  • Optional Git sync per environment
  • GitHub, Bitbucket or any Git repository

Before you start

Who it is for

  • Automic teams that move changes between several environments or clients and need a clear rollback path
  • Regulated or change-controlled organisations that require a second approval and a complete audit log
  • Large development groups that work in parallel on the same Automic system

Technical requirements

  • Automic Automation Engine V21 or higher, connected through the Automic Java API over TLS
  • One or more configured Automic clients per instance
  • On-premise: Windows or Linux (64-bit) with Java (OpenJDK), Apache Tomcat 10 and PostgreSQL 15
  • Exact versions, ports and both installation paths are described in the Full Guide.

Licensing & price

  • Time-limited subscription, typically for 1, 2 or 3 years
  • Product updates, new feature releases and Tricise technical support included for the full term
  • Pricing scales with the number of managed Automic environments and is provided on request
  • In the Tricise Service Tiers, the full 3C Release Manager is part of Platinum.

Light Edition or full version?

The Light Edition gives you transparency across your environments. The full version adds transports, bulk changes, the four-eyes principle and Git integration.

FunctionLight EditionFull version
Object management✓✓
DEV ↔ PROD diffs✓✓
Scheduled snapshots✓✓
Audit trail✓✓
Recursive transports with deep scan—✓
Bulk changes—✓
Four-eyes principle—✓
Git/Bitbucket integration (optional)—✓
Included in the Tricise Service TiersSilver & GoldPlatinum

Only need to compare your environments? Take a look at the 3C Release Manager Light Edition.

Videos & documentation

Documentation

Further reading on the 3C Release Manager:

Frequently asked questions

Which Automic versions does the 3C Release Manager support?

Automic Automation Engine V21 or higher. The integration uses the Automic Java API over TLS-secured communication.

How does a rollback work?

Every deployment automatically creates a backup snapshot before it runs and a validation snapshot afterwards. The Rollback button creates a rollback deployment that is the exact opposite of the original one and restores the affected objects from the backup snapshot. It is started manually, like any other deployment.

Can several teams work in parallel without overwriting each other’s changes?

Yes. The Conflict Analysis tab of every user story lists all other user stories that change the same configuration items, so conflicts become visible before deployment.

How does the Git integration work?

An administrator stores the repository URL and the connection method (credentials or SSH key). For each environment you set a branch and enable Git Sync. From then on, every successful snapshot is committed and pushed to that branch automatically. GitHub, Bitbucket and any other Git repository are supported.

What is the difference between the Light Edition and the full version?

The Light Edition covers object management, DEV ↔ PROD diffs, scheduled snapshots and an audit trail. The full version adds recursive transports with deep scan, bulk changes, the four-eyes principle and optional Git/Bitbucket integration, and is available as SaaS or on-premise.

How is the 3C Release Manager licensed?

As a time-limited subscription, typically for 1, 2 or 3 years, including updates and Tricise technical support. Pricing scales with the number of managed Automic environments and is provided on request.

Ready to move forward

Book a quick 30-minute session to turn your ideas into action and uncover what’s possible with the right partner by your side.

Scroll to Top