Bamboo Artifactory Plugin (Legacy)
Maintain legacy Bamboo Artifactory Plugin plans and migrate new work to JFrog CLI.
Migrate first: For new Bamboo work, run JFrog CLI from Bamboo Script or Command tasks. Neither Bamboo plugin is certified for Bamboo Data Center 12.x. Plan migration from Bamboo Data Center before its end of life.
This historical page serves existing plans that use the Bamboo Artifactory Plugin. The code still defines Generic Resolve, Generic Deploy, Publish Build Info, build-tool, and release-management features. The Bamboo Artifactory Plugin is a separate, superseded product from the current Bamboo JFrog Plugin, so don't treat the two as interchangeable.
This page covers the following tasks:
Keep an Existing Plan Running
Existing plans that use the Bamboo Artifactory Plugin can keep running while you plan migration. This procedure captures the current plan configuration and confirms that build-info still publishes as expected. For more information about the data these tasks publish, see About Build Info.
To keep an existing plan running:
- Record the configured Artifactory server, credentials source, resolver repository, deploy repository, build name, and build number.
- Keep existing plugin tasks in their current order. Plans created around older plugin releases can differ in when build-info is published.
- For plans that aggregate build-info, retain Artifactory Publish Build Info after the tasks that collect it.
- Confirm the build result links to the expected build-info in Artifactory.
- Test plugin or Bamboo upgrades in staging before changing production plans.
For exhaustive legacy task configuration, see the Bamboo Artifactory Plugin source. This page covers a focused subset of that configuration and isn't a starting point for new plans.
Move a Task to JFrog CLI
Each legacy plugin task can move to JFrog CLI in a standard Bamboo Script or Command task. This procedure moves one task at a time, so you can compare the JFrog CLI result with the plugin result before you remove the legacy task.
To move a task to JFrog CLI:
- Translate the task's resolve, upload, or build-info action to a documented JFrog CLI command.
- Store the access token in Bamboo's secret mechanism.
- Run the command in a Script or Command task with explicit build name and number.
- Compare artifact paths and build-info with the plugin-generated run.
- Remove the legacy task only after the comparison passes.
Troubleshooting
The following table lists common symptoms, their likely causes, and the action to take.
| Symptom | Likely cause | Action |
|---|---|---|
| Build-info is missing | Publish Build Info is absent or ordered before collecting tasks | Place it after tasks that collect build-info. |
| Upload or download is denied | The Bamboo identity lacks repository permissions | Verify read and deploy permissions for the selected repository. |
| A Bamboo Data Center 12.x upgrade breaks the plugin | The plugin is not certified for Bamboo Data Center 12.x | Use JFrog CLI tasks as an interim path and proceed with continuous integration migration planning. |
Related Topics
Updated 16 days ago