Auto-Promotion
Learn how Auto-Promotion in JFrog AppTrust promotes an application version to the next stage when the evidence its policies require has arrived.
Auto-Promotion is an application setting in JFrog AppTrust that promotes an application version to the next stage when the evidence its policies require has arrived. You can turn it on in Step 2 of the Create Application wizard, and you can change it later when you edit the application. Auto-Promotion is off by default. Until you turn it on and select at least one stage, you promote versions manually.
Why Auto-Promotion Matters
Evidence, such as SBOMs, test reports, and attestations, can arrive at different times. Without Auto-Promotion, someone or something must check back and promote the version after the evidence is in place. Auto-Promotion removes that wait, so a version that meets its requirements moves on without a manual step.
How Auto-Promotion Works
You choose the stages that AppTrust auto-promotes versions from. AppTrust promotes a version in a selected stage to the next stage in the lifecycle. AppTrust promotes a version in Unassigned to the first stage. When you select the stage before PROD, AppTrust releases its versions to PROD. The list of stages does not include PROD, because versions only move into PROD through a release.
AppTrust attempts an auto-promotion when:
- New evidence arrives for the version.
- You promote the version manually, or finalize a draft by promoting it.
- You create an application version (not a draft).
When a version has all the evidence the next stage requires, AppTrust attempts to promote it. The promotion succeeds only if the version passes the gates. The next time evidence arrives, AppTrust tries again.
Cascading Promotions
After a successful auto-promotion, AppTrust checks the new stage. If that stage is also selected and the version has the evidence required, the version moves on to the next stage. A version can move through several consecutive selected stages in one run.
Auto-Promotion Details
Each auto-promotion runs as the system user system:auto-promote, so it does not depend on the promote permissions of the user who created the version. It copies the artifacts to the target stage and uses the signing key of the application version. Each auto-promotion appears in the activity log as an Auto promote application version event.
The Auto-assign option in the version creation wizard is a separate setting. It assigns a new version to the first stage when you create it, but only if the version's artifacts are already in that stage's repositories, and the version passes the stage's gates. Otherwise, the version stays in Unassigned. Auto-Promotion, by contrast, copies the artifacts to each target stage. After the version is created, Auto-Promotion continues from the stage the version is in.
What's Next?
Learn how to Create an Application with Auto-Promotion.
Updated about 22 hours ago
