# Publish from Bitbucket Pipelines

> Publish Maven, Gradle, npm, Python and Docker artifacts to CloudRepo from a Bitbucket Pipelines build, with a repository token held as a secured repository variable.

A Bitbucket Pipelines build publishes to CloudRepo the way your laptop does: the build tool sends a repository token with the upload. What changes is where the token lives. Keep it in a secured repository variable, which Bitbucket gives every build as an environment variable, and let a committed config file name that variable instead of holding the token.

## Before you start

- A repository, and a [repository token](/docs/authenticate/repository-tokens.html) that reaches it. A token that publishes is **Read + write**; a build that only pulls needs **Read only**.
- A token you create under **Repository Tokens** belongs to your account. Deleting a user from your organization deletes that user’s tokens, and any build using one stops authenticating. So create the token as an account that outlives any one person: a user you make for builds (see [Create Your First User](/docs/get-started/add-users.html)), signed in to the admin portal when it mints the token. The owner can instead create a [service key](/docs/authenticate/repository-tokens.html#service-keys-for-your-pipelines), which belongs to your organization rather than to a user.
- Your repository URL, `https://your-org.mycloudrepo.io/repositories/your-repo`, and the username that Maven, Gradle, Python and Docker clients send: the email address of the account that created the token. npm sends the token alone.

## Store the token as a variable

1. In your Bitbucket repository, open **Repository settings**, then under **Pipelines** choose **Repository variables**.
2. Enter `CLOUDREPO_TOKEN` as the name and the token as the value, tick **Secured**, and click **Add**.

Bitbucket hides a secured variable’s value in build logs, and a secured variable can be replaced or deleted but not edited. A build reads the variable as `$CLOUDREPO_TOKEN`, which is how the files below get it. To share one token across repositories, Bitbucket also keeps variables for a workspace. See [Variables and secrets](https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/) in Atlassian’s documentation.

Keep the token off the command line, which logs and process listings can show. The blocks on this page pass it through the environment or a file the tool reads.

## Publish from a pipeline

Pick your client. The choice is remembered on every page of these docs. Each tab has the same parts: a file that names the token’s variable, the repository settings of your build, and the `bitbucket-pipelines.yml`. Commit them; none holds the token. Each pipeline runs when you push a tag that starts with `release-`.

**Maven**

Maven reads the credential from a settings file. Commit this one as `.mvn/settings.xml`; `${env.CLOUDREPO_TOKEN}` is replaced by the environment variable when Maven runs. Replace `you@example.com` with the email address of the account that created the token.

`.mvn/settings.xml`

```xml
<settings>
  <servers>
    <server>
      <id>cloudrepo</id>
      <username>you@example.com</username>
      <password>${env.CLOUDREPO_TOKEN}</password>
    </server>
  </servers>
</settings>
```

The `<id>` must match the repository’s `<id>` in your `pom.xml`. `<distributionManagement>` is where `mvn deploy` publishes:

`pom.xml`

```xml
<distributionManagement>
  <repository>
    <id>cloudrepo</id>
    <url>https://your-org.mycloudrepo.io/repositories/your-repo</url>
  </repository>
</distributionManagement>
```

The step runs in a Maven image on a tag push and passes the settings file with `--settings`:

`bitbucket-pipelines.yml`

```yaml
pipelines:
  tags:
    'release-*':
      - step:
          name: Publish to CloudRepo
          image: maven:3.9-eclipse-temurin-17
          script:
            - mvn --batch-mode --settings .mvn/settings.xml deploy
```

Expected: the step ends with `BUILD SUCCESS`, and the artifact is listed in the repository in the [admin portal](https://admin.cloudrepo.io). To resolve dependencies from the same repository in a build, add a `<repositories>` block with the same URL; see [Maven Repositories](/docs/formats/maven.html).

**Gradle**

Gradle reads the token from the environment in the build script. Replace `you@example.com` with the email address of the account that created the token.

`build.gradle.kts`

```kotlin
publishing {
    publications {
        create<MavenPublication>("library") {
            from(components["java"])
        }
    }
    repositories {
        maven {
            url = uri("https://your-org.mycloudrepo.io/repositories/your-repo")
            credentials {
                username = "you@example.com"
                password = providers.environmentVariable("CLOUDREPO_TOKEN").orNull
            }
        }
    }
}
```

`.orNull` keeps every other Gradle command working on a machine where the variable is not set; only `publish` needs it. Add the `java-library` and `maven-publish` plugins to the `plugins` block if your build does not have them.

`bitbucket-pipelines.yml`

```yaml
pipelines:
  tags:
    'release-*':
      - step:
          name: Publish to CloudRepo
          image: gradle:jdk17
          script:
            - gradle publish
```

If your project has the Gradle wrapper, run `./gradlew publish` instead. A Groovy build script takes the same `maven { ... }` block under `publishing { repositories { ... } }`, with the credential read from `System.getenv("CLOUDREPO_TOKEN")`.

**npm**

npm replaces `${CLOUDREPO_TOKEN}` in `.npmrc` with the environment variable of that name, so this file can be committed. Keep the trailing `/` on both lines, and keep the second line identical to the registry URL without `https:`.

`.npmrc`

```ini
registry=https://your-org.mycloudrepo.io/repositories/your-repo/
//your-org.mycloudrepo.io/repositories/your-repo/:_authToken=${CLOUDREPO_TOKEN}
```

npm sends the token on its own, so there is no username to set.

`bitbucket-pipelines.yml`

```yaml
pipelines:
  tags:
    'release-*':
      - step:
          name: Publish to CloudRepo
          image: node:24
          script:
            - npm publish
```

The same `.npmrc` and variable serve `npm ci` and `npm install` in a build that only pulls. For a scoped package, or a repository that sits beside the public registry, see [npm Repositories](/docs/formats/npm.html).

**pip**

twine uploads a built package. It reads its username and password from `TWINE_USERNAME` and `TWINE_PASSWORD`, which the step sets from the variable, and takes the repository URL without `/simple/`. Replace `you@example.com` with the email address of the account that created the token.

`bitbucket-pipelines.yml`

```yaml
pipelines:
  tags:
    'release-*':
      - step:
          name: Publish to CloudRepo
          image: python:3
          script:
            - pip wheel . --no-deps -w dist
            - pip install twine
            - export TWINE_USERNAME=you@example.com
            - export TWINE_PASSWORD="$CLOUDREPO_TOKEN"
            - twine upload --repository-url https://your-org.mycloudrepo.io/repositories/your-repo dist/*
```

To install from the repository in a build, set `PIP_INDEX_URL` from the variable rather than passing `--index-url`, which would put the token on the command line. See [Repository Tokens](/docs/authenticate/repository-tokens.html) for the URL, and write the `@` in your email address as `%40`.

**Docker**

Log in to the host alone, with your email address and the token on standard input, then build and push. The image reference carries the repository after the host. Bitbucket gives a step a Docker daemon when the step lists the `docker` service.

`bitbucket-pipelines.yml`

```yaml
pipelines:
  tags:
    'release-*':
      - step:
          name: Publish image to CloudRepo
          services:
            - docker
          script:
            - echo "$CLOUDREPO_TOKEN" | docker login your-org.mycloudrepo.io --username you@example.com --password-stdin
            - docker build -t your-org.mycloudrepo.io/repositories/your-repo/my-app:1.0.0 .
            - docker push your-org.mycloudrepo.io/repositories/your-repo/my-app:1.0.0
```

Use your own image name and tag. The password is the repository token, not a portal password. More: [Docker Repositories](/docs/formats/docker.html), and [Run Docker commands in Bitbucket Pipelines](https://support.atlassian.com/bitbucket-cloud/docs/run-docker-commands-in-bitbucket-pipelines/).

## When publishing fails

- **`401 Unauthorized`.** The credential was refused. The username must be the email address of the account that created the token, and the token must not be expired or revoked. Check that the variable is named `CLOUDREPO_TOKEN` and that its value is the whole token (a secured variable can be replaced but not edited, so replace it if you are unsure). The full list is on [Repository Tokens](/docs/authenticate/repository-tokens.html#when-a-client-answers-401-403-or-404).
- **`403 Forbidden`.** The token does not reach this repository, or it is **Read only** and the build publishes. Create a **Read + write** token that includes the repository.
- **`409 Conflict` from `mvn deploy`.** The release version you are publishing already exists, and Overwrite Protection refuses to replace it. Publish a new version, or use a `-SNAPSHOT` version while you iterate. See [Maven Overwrite Protection](/docs/formats/maven.html#maven-overwrite-protection). Python repositories have the same setting: [Python Repositories](/docs/formats/python.html#overwrite-protection).

---

The page: https://www.cloudrepo.io/docs/ci/bitbucket-pipelines.html