The basic workflow for using Artifactory for Release Lifecycle Management is described below.
One-time Release Bundle v2 Setup by an Administrator
# | Procedure | Using Platform UI | Using APIs |
---|---|---|---|
1 | Create custom global and project environments, if required | POST ${baseUrl}/v1/environments POST ${baseUrl}/v1/projects/{project_key}/environments | |
2 | Assign repositories to each environment | Update Repository Configuration Based on changes made in the Repository Configuration JSON. | |
3 | [Enterprise+] Connect Distribution Edge nodes to the JFrog platform | POST /mc/api/v1/jpds | |
4 | Generate and upload signing keys to Artifactory | POST /api/security/keypair | |
5 | [Enterprise+] Propagate signing keys to the Edge nodes | Not available using the UI. For more information, see: | POST /lifecycle/api/v2/distribution/key/propagate/{key_name} |
6 | Create webhooks for Release Bundle creation and promotion events (optional) |
Working with Release Bundles v2
# | Procedure | In Platform UI | Using APIs |
---|---|---|---|
1 | Create a Release Bundle v2 | POST /lifecycle/api/v2/release_bundle | |
2 | Promote a Release Bundle v2 from one environment to the next | Promote Release Bundle Version POST /lifecycle/api/v2/promotion/records/{name}/{version} | |
3 | [Enterprise+] Distribute the Release Bundle v2 | Distribute Release Bundle Version V2 POST /lifecycle/api/v2/distribution/distribute/{release_bundle_name}/{release_bundle_version} |
Tip
The JFrog CLI includes commands to facilitate the Release Lifecycle Management process. For more information, see CLI for JFrog Release Lifecycle Management.