Bitbucket Mock/Dev(ficustree)
Configuration

Bitbucket & Release Settings

Manage Bitbucket Cloud API authentication, workspace tokens, and automated branching preferences.

Local Simulation (Mock Mode)

Target Workspace: ficustree

Running smoothly.

Operating Mode
Authenticated AccountN/A
API Rate Limit1000 / 1000 reqs

Bitbucket Authentication Setup Guide

Bitbucket offers two primary ways to authenticate API microservices:

Option 1: Personal App Password (Recommended)Standard
  1. Log into Bitbucket, click on your Profile Avatar (top-right) → Personal settings.
  2. In the left sidebar under Access management, click App passwords.
  3. Click Create app password.
  4. Label: Athena-Release-Management
  5. Select the required permissions:
    • Repositories: Read, Write, Admin, Delete
    • Projects: Read
    • Pull requests: Read, Write
    • Pipelines: Read, Write
  6. Save and copy the generated 24-character password into athena/.env.local.
Option 2: Workspace Access TokenWorkspace Level

If your organization manages tokens at the workspace level, you can generate a Workspace Access Token by going to your workspace settings in Bitbucket → Access tokens.

Sample .env.local Configuration
# Athena Bitbucket Cloud Configuration (.env.local)
BITBUCKET_WORKSPACE=ficustree

# Option A: Personal App Password
BITBUCKET_USERNAME=your-bitbucket-username
BITBUCKET_APP_PASSWORD=your-app-password

# Option B: Workspace Access Token
# BITBUCKET_ACCESS_TOKEN=your-bearer-token

DEFAULT_MAIN_BRANCH=main
DEFAULT_DEVELOP_BRANCH=develop
AUTO_INIT_BRANCHES=true

Default Branching Strategy Configuration

Athena is configured to ensure that every new repository automatically provisions both standard branches:

mainActive

Production release branch. Protected against direct commits.

developActive

Integration and staging branch. Created automatically from main.