release-aa-backend-prod

Automate the Automation Analytics backend production release via deploy-clowder.yml, Jira, and GitLab merge request.

2|Updated Feb 16, 2026

Search Tags:#automation #deployment #production #backend #release #jira #app-interface

Ready to run

npx skills add https://github.com/dmzoneill/skills --skill release-aa-backend-prod

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-aa-backend-prod
Source: https://github.com/dmzoneill/skills/tree/main/release-aa-backend-prod
Command: npx skills add https://github.com/dmzoneill/skills --skill release-aa-backend-prod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of releasing the Automation Analytics backend to production, streamlining deployments and ensuring consistency.

Core Features & Use Cases

Automated Deployment: Updates deployment configurations, creates Jira issues, and initiates Merge Requests for approval.
Verification: Ensures the commit exists and the corresponding Docker image is available on Quay.
Use Case: When a new version of the AA backend is ready, use this skill to automatically handle the release process, from updating configuration files to notifying the team.

Quick Start

Release the AA backend to production using commit SHA 'abcdef123456'.

Frequently Asked Questions about release-aa-backend-prod

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate a backend production release with Jira and GitLab merge requests?▼

Automating a backend production release involves updating deployment configuration files, creating a Jira issue, and generating a GitLab merge request for approval. This skill handles the entire workflow automatically after verifying prerequisites.

What checks are needed before deploying a backend to production via GitLab?▼

Before deploying to production, you need to verify that the specific commit exists and that the corresponding Docker image is available on Quay. These checks ensure the release target is valid and ready.

How does app-interface handle backend deployment configuration updates?▼

App-interface handles deployment configuration updates by modifying the deploy-clowder.yml file. This updates the production configuration to point to the new release version before initiating the Jira and GitLab workflow.

Can I release a backend to production using just a commit SHA?▼

Yes, you can release a backend to production using a commit SHA like 'abcdef123456'. The automation validates the commit, checks Quay for the image, updates deploy-clowder.yml, and creates the necessary Jira issue and GitLab merge request.

Why does my automated production release fail before creating a Jira issue?▼

An automated production release fails before creating a Jira issue if the commit SHA does not exist or the corresponding Docker image is not yet available on Quay, preventing invalid or incomplete deployments.