Overview

Highly customizable ETRM platforms like ION Group’s Allegro offer flexibility for energy companies but managing deployments of these customizations presents ongoing challenges. Manual, multi-step processes, often dependent on experienced administrators, make deployments error-prone and time-consuming. Lucido Group implemented a custom deployment API and integrated it with Git and CI/CD pipelines to streamline deployments, increase reliability, and reduce manual effort. This white paper outlines the solution architecture, deployment options, and the measurable outcomes seen at a client with high development activity and frequent deployments.

Background & Problem Statement

Allegro is a widely used Energy Trading and Risk Management (ETRM) platform, favored for its extensibility. Many businesses customize their Allegro instances to meet operational needs, including:

• Data Model Extensions – New or updated tables, columns, and constraints
• UI Customizations – Enhanced views and reports
• Custom Business Logic – Background jobs and stored procedures
• System Integrations – External interfaces such as ICE, Trayport, and CME

While powerful, Allegro’s customization model introduces deployment complexity. Traditional deployment involves manually applying XML files, executing database scripts, recycling application pools, and restarting integration processes. Common issues include:

• Human Error – Missed steps, out of sequence execution, or forgotten components
• Feature Conflicts – Overlapping changes from parallel workstreams
• Rollback Difficulty – Manually reverting changes adds even more complexity
• Lack of Traceability – Unclear audit trail for who deployed what and when

Solution Overview

To address these challenges, Lucido implemented a custom deployment API, written in C#/.NET, designed specifically for Allegro environments. The API performs three primary functions:

1. Generate Release

• Consolidates XML-based configuration files into logical packages
• Packages include steps such as table modifications, class updates, views, templates, and constraints
• Follows Allegro’s standard XML structure and invokes web methods over SOAP

2. Deploy

• Automatically applies the XML files to a target environment
• Executes deployments in the correct sequence and checks for compile errors
• Creates backups of existing components to support rollback if needed

3. Rollback

• Restores the prior state using backups taken during the deployment
• Reverts only the affected components

Each release is composed of one or more packages, and each package includes a sequence of steps. This structure enables granular control while maintaining consistency.

Flexible Release Strategies

The API offers flexibility in how releases are structured and deployed. Clients can choose to create tightly scoped releases that include only the incremental changes made since the last deployment, or they can bundle files based on functional components, business modules, or features. This flexibility allows teams to align their deployment strategy with their development workflow, whether that is agile iteration or modular delivery.

Release Strategy Comparison

Deployment Approaches

The deployment solution supports two usage models depending on the client’s maturity and needs:

A. Git + CI/CD Integration

For teams with strong technical expertise and experience, the DevOps API is fully integrated with GitHub and a CI/CD pipeline. CI/CD platform integration is flexible enough to implement iterative delivery by leveraging an automated diff analysis or modular deployments based on repository structure. While Allegro’s native XML structure limits traditional Git-based workflows, the DevOps API integration unlocks modern CI/CD capabilities previously unavailable in Allegro environments.

Advantages and Best Practices

• Version Control & Code Reviews – All changes are tracked through Git, enabling pull requests and peer reviews prior to merge. Provides line-by-line visibility into changes.
• Deployment Approvals & Audits – Environments such as test, staging, and production can require approval gates, ensuring oversight and control.
• Clear and Transparent Audit – All code changes are clearly tracked by who made the change and when it was deployed.
• Automated Artifact Management – Deployment artifacts are automatically generated, versioned, and traceable across environments.
• Repeatability & Reliability – The CI/CD pipeline enforces consistent build and deployment steps, minimizing human error.
• Upgrade Compatibility – Changes deployed to production via CI/CD are tracked in version control, making them easy to integrate into future upgrades or parallel long-running projects

Workflows and pipelines on CI/CD platforms are fully customizable, enabling a development and deployment process that is compatible with any organization and their needs. Teams control their approval policies, environment specific workflows, and order of workflow procedures – for instance, whether technical review happens before, after or in parallel with business validation.

Sample Workflow

1. Developer works on an isolated feature branch.
2. Feature branch is deployed to a test environment for business validation. Optionally the deployment to test is behind an approval gate.
3. Pull request is created for technical review.
4. Optionally features are grouped into a release branch and deployed together.
5. Production deployment triggered automatically on merge to the main branch, or manually from a release branch. Approval is required before execution.

B. Manual User Interface

For organizations with lighter development/deployment needs or less CI/CD experience, the API can be paired with a user-facing interface.

• Users (typically system administrators) select the XML files to include in a release
• The tool allows them to deploy or roll back changes with a few clicks
• No Git or pipeline integration is optional

Key Benefits

• Lower implementation complexity
• Easier adoption for clients unfamiliar with DevOps tooling
• Rapid enablement for teams with fewer deployments
• Accessible to administrators less experienced on Allegro, Git and CI/CD

CI/CD vs. Manual UI: Pros & Cons

Outcomes & Benefits

At a large energy client with extensive Allegro customizations, this deployment solution produced immediate, measurable benefits:

• Deployment Preparation Time Reduced – Manual packaging from GitHub replaced by automated CI process
• Faster Time to Deploy – Once a release branch is merged, production deployments run in minutes
• Improved Reliability – Backups and rollback allow safe experimentation
• Increased Traceability – Git history and CI logs ensure clear visibility into changes
• Scalability – Supports growing number of XML files and feature branches

Conclusion

Manual Allegro deployments have historically been a fragile, expert-driven process – particularly for organizations with significant customizations. Lucido Group’s custom deployment API, integrated with Git-based workflows or a simple UI, allows organizations to modernize their Allegro deployment strategy with the same principles used in broader software engineering. Whether adopting a full CI/CD pipeline or a lightweight manual deployment model, clients benefit from improved reliability, reduced deployment time, and greater operational confidence.