deploy-qa

name	deploy-qa
description	Deploy to QA environment (QA1 or QA2). Use when deploying code to the QA testing environments via GitHub Actions. Includes pre-deployment checks for persistence.xml.
disable-model-invocation	true
allowed-tools	Bash, Read, Grep
argument-hint	[qa1|qa2]

Deploy to QA Environment

Deploy the latest development code to QA1 or QA2 via GitHub Actions.

Arguments

• $0 - Target environment: qa1 or qa2

Pre-Deployment Checklist

Before deploying, MUST verify:

1. persistence.xml uses environment variables — read src/main/resources/META-INF/persistence.xml and confirm both <jta-data-source> values are ${JDBC_DATASOURCE} / ${JDBC_AUDIT_DATASOURCE}, not a hardcoded local JNDI name (e.g. jdbc/coop, jdbc/ruhunuAudit)
2. No hardcoded DDL generation paths — no eclipselink.application-location pointing at c:/tmp/ or /home/*/tmp/
3. All changes committed and pushed

Deployment Process

QA1 Deployment

# Merge development into qa1 branch
git fetch origin
git checkout qa1
git merge origin/development
git push origin qa1

QA2 Deployment

# Merge development into qa2 branch
git fetch origin
git checkout qa2
git merge origin/development
git push origin qa2

GitHub Actions will automatically:

1. Build the application with Maven
2. Deploy to the target QA server
3. Restart the Payara application server

Post-Deployment

• Monitor GitHub Actions for build status
• Check QA environment is accessible after deployment
• Verify the deployed feature works as expected

Troubleshooting

If deployment fails:

1. Check GitHub Actions logs for build errors
2. Verify persistence.xml configuration
3. Check if QA server is accessible
4. See QA Troubleshooting Guide