ARTIFACTORY: How to Move Release Bundles Back to the Global (Default) Project in JFrog Artifactory

Introduction

There are two scenarios in which Release Bundles may need to be moved back to the global (default) project:

Release Bundles were originally created in the global (default) project, but later became associated with another project after the release-bundles-v2 repository was assigned to that project.

Release Bundles were created directly within a project, where they are stored in the project's dedicated Release Bundle repository (for example, <project-key>-release-bundles-v2).

This article explains the steps required for each scenario.



Scenario 1 – Release Bundles Originally Created in the Global Project

Overview

Release Bundles created under the global (default) project are stored in the global release-bundles-v2 repository.

If the release-bundles-v2 repository is later assigned to another project, the Release Bundles become associated with that project's scope and are no longer visible under the global project.

To restore them to the global (default) project, reattach the release-bundles-v2 repository to the global project.



Prerequisites

Admin-level access to your JFrog instance.

A valid admin token (Identity Token or Access Token with admin privileges).

Confirm that your release bundles are stored in the release-bundles-v2 repository (navigate to All Projects → Artifactory → Artifacts and look for release-bundles-v2).



Steps



Step 1 – Verify the Repository Location

```
Log in to your JFrog Platform.
```

Navigate to All Projects → Artifactory → Artifacts.

Confirm that the release-bundles-v2 repository is listed and is currently assigned to a non-global project.

Step 2 – Generate an Admin Token

Go to Administration → Identity and Access → Access Tokens.

Generate a new token with Admin scope, or use an existing admin token.



Step 3 – Run the curl Command

Use the appropriate command based on your deployment type:

Important:

JFrog Cloud enforces HTTPS. Using http:// will result in a 301 Moved Permanently redirect from the Nginx layer, causing the request to fail. Always use https://.

Shell

curl -X PUT
"https://<your-instance>.jfrog.io/access/api/v1/projects/_/attach/repositories/release-bundles-v2/default?force=true" \
  -H "Authorization: Bearer <ADMIN_TOKEN>"

Replace:

<your-instance> → your JFrog Cloud instance name (e.g., mycompany)

<ADMIN_TOKEN> → your admin access token



Step 4 – Verify the Result

After running the command successfully, navigate back to All Projects → Artifactory → Release Lifecycle.

Confirm that the release bundles are now visible under the global project.

Scenario 2 – Release Bundles Were Created Directly Inside a Project

Overview

Release Bundles created inside a project are stored in that project's dedicated Release Bundle repository (for example, <project-key>-release-bundles-v2).

Since these Release Bundles belong to the project, reattaching repositories will not move them to the global project.

Instead, recreate each Release Bundle in the global (default) project by using the existing project Release Bundle as the source.

Recreate each release bundle in the global/default project by using the existing project bundle as the source. Omitting the X-JFrog-Project header ensures the new bundle lands in the global scope.

Note:

Do not include the X-JFrog-Project header. Omitting this header creates the new Release Bundle in the global (default) project



Recreate the Release Bundle

Run the following command for each Release Bundle.

Replace:

```
<bundle-name>
```
```
<version>
```
```
<PROJECT_KEY>
```

curl -X POST "https://<JFROG_URL>/lifecycle/api/v2/release_bundle" \
  -H "Authorization: Bearer <ADMIN_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "release_bundle_name": "<bundle-name>",
    "release_bundle_version": "<version>",
    "source_type": "release_bundles",
    "source": {
      "release_bundles": [
        {
          "project_key": "<PROJECT_KEY>",
          "release_bundle_name": "<bundle-name>",
          "release_bundle_version": "<version>"
        }
      ]
    }
  }'

After the command completes successfully, verify that the newly created Release Bundle belongs to the global (default) project.

The response should include:

"repository_key": "release-bundles-v2"

This confirms that the Release Bundle has been created in the global Release Bundle repository.