CI/CD for APEX with GitHub Actions
Put your APEXLang app under source control and ship it on every push with an automated pipeline.
Advanced⏱ 1 min readUpdated: 2026-06-09
Once your app is APEXLang files in Git, you can deploy it automatically. A GitHub Actions workflow installs SQLcl, connects with secrets, and imports the app on every push to main.
Store the app as files
Commit the split .apx export so every change is a reviewable diff.
git add app100/ git commit -m "feat: add status filter to orders page" git push
The deploy workflow
name: deploy-apex
on: { push: { branches: [main] } }
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install SQLcl
run: |
curl -L -o sqlcl.zip https://download.oracle.com/otn_software/java/sqldeveloper/sqlcl-latest.zip
unzip -q sqlcl.zip
- name: Import app
env:
DB_URL: ${{ secrets.DB_URL }}
DB_USER: ${{ secrets.DB_USER }}
DB_PWD: ${{ secrets.DB_PWD }}
run: |
./sqlcl/bin/sql -L $DB_USER/$DB_PWD@$DB_URL @deploy.sql⚠ Secrets, not commits
Database credentials go in GitHub Actions secrets — never commit them. Use a deploy user with least privilege.
Check your understanding
Check your understanding
0% · 0/2What makes APEX CI/CD possible?
Where do DB credentials belong?
Need this delivered?
Request a quote