Hello, Consider this usecase: * Deployed Migration 001 along with Feature F01 as a major version (v2.0.0) * A month later i added a small enhancement F02 that required Migration 002, the upgrade was decided to be a minor version update by forge (v2.1.0) * When I release the forge application to my atlassian site, the migration was not run. I searched the atlassian documentation and asked the Forge AI Help assistant, but its answers (scheduled hourly trigger, lazy migrations, and adding a web trigger) did not convince me as the way to go. My goal is for forge to execute my migrations queue everytime I deploy my application, regardless of version. What is the recommended way to achieve my goal? Thank you, Ray

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Running DB migrations on minor version deployment

Ray Haddad

Hello,

Consider this usecase:

Deployed Migration 001 along with Feature F01 as a major version (v2.0.0)
A month later i added a small enhancement F02 that required Migration 002, the upgrade was decided to be a minor version update by forge (v2.1.0)
When I release the forge application to my atlassian site, the migration was not run.

I searched the atlassian documentation and asked the Forge AI Help assistant, but its answers (scheduled hourly trigger, lazy migrations, and adding a web trigger) did not convince me as the way to go.

My goal is for forge to execute my migrations queue everytime I deploy my application, regardless of version.

What is the recommended way to achieve my goal?

Thank you,

Ray

Accepted answers

Ray Haddad

Hello,

Thank you for your response.

I will post this question in the developer community.
Thank you!

All comments

Tomislav Tobijas

Hi @Ray Haddad,

This looks more related to Forge / Forge SQL than to Confluence itself > this question is currently posted in the Confluence section of the Community.

You may have better luck posting this in the Atlassian Developer Community, where the Forge team and other Forge developers are more active. 👀

The Forge SQL documentation may also be useful here, particularly the section on schema management: https://developer.atlassian.com/platform/forge/storage-reference/sql/

Hope this points you in the right direction!

Cheers,
Tobi

Numeric Oasis

Your diagnosis is right, and the Forge SQL docs state the cause outright: avi:forge:upgraded:app is sent only when the app is upgraded to a new major version, and does not trigger on minor or patch upgrades. Adding a migration does not change your manifest, so Forge bumps you to v2.1.0 and no trigger ever fires. See Orchestrate schema updates: https://developer.atlassian.com/platform/forge/storage-reference/sql-api-schema/

The same page says what to do about it: if you add new DDL operations in a minor or patch release, use a scheduled trigger or another mechanism to ensure migrations run. So the scheduled trigger is the documented answer for your exact case, not a workaround someone invented.

It is also less blunt than it sounds. Forge SQL tracks queued DDL operations by operationName and checks each installation hourly for pending or failed ones, re-running those and skipping what already applied. An hourly trigger therefore converges the queue after a deploy rather than running blindly.

There is no deploy event to hook, though, so running on every deploy is not achievable directly. Convergence shortly after deploy is.

The shape the docs recommend for production is a queue plus an async event consumer, pushed from both the install or upgrade trigger and a scheduled trigger. The consumer gets 15 minutes instead of the 55-second function timeout, which matters against the 25 DDL requests per minute per-install limit. Wrap migrationRunner.run() in retry logic with a 60-second timeout and keep every statement idempotent.

Agreed with Tomislav that developer.atlassian.com is the better venue for follow-ups.

Ray Haddad

Hello Tomislav,
I will post this question in the developer community.
Thank you!

Ray Haddad

Hello,

Thank you for your response.

I will post this question in the developer community.
Thank you!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

version

database

database-migration