Deploy Bitbucket & Jira on Azure(Docker)

This guide helps you deploy Bitbucket and Jira on Azure using Docker, with a shared PostgreSQL database.

1️⃣ Set Up Azure Resources

Create an Azure Resource Group and provision two virtual machines:

• Bitbucket VM - Hosts Bitbucket
• Use Ubuntu 22.04 LTS.
• Minimum 4 vCPUs, 16GB RAM.
• SSD 1TB.
• Open required ports: 7990, 7999, 22, 80.
• Jira VM - Hosts Jira
• Use Ubuntu 22.04 LTS.
• Minimum 4 vCPUs, 16GB RAM.
• SSD 500GB.
• Open required ports: 8080, 22, 80.
• PostgreSQL Database - Will be shared between both services
• Minimum 2 vCPUs, 8GB RAM.
• SSD 128GB.
• Open required ports: 5432, 22, 80.

2️⃣ Configure PostgreSQL Database

Set up a managed PostgreSQL database on Azure and create separate databases for Bitbucket and Jira.

CREATE DATABASE bitbucket_db;
CREATE DATABASE jira_db;

CREATE USER bitbucket_user WITH PASSWORD 'StrongBitbucketPassword';
CREATE USER jira_user WITH PASSWORD 'StrongJiraPassword';

GRANT ALL PRIVILEGES ON DATABASE bitbucket_db TO bitbucket_user;
GRANT ALL PRIVILEGES ON DATABASE jira_db TO jira_user;

3️⃣ Install Docker on Both VMs

Ensure Docker and Docker Compose are installed on both virtual machines.

sudo apt update && sudo apt upgrade -y
sudo apt install -y docker.io docker-compose
sudo systemctl enable docker && sudo systemctl start docker
# Install Git LFS
sudo apt update
sudo apt install git-lfs -y
# Enable Git LFS
git lfs install
mkdir -p /opt/atlassian/bitbucket /opt/atlassian/jira
chown -R 2001:2001 /opt/atlassian/bitbucket # For Bitbucket
chown -R 2002:2002 /opt/atlassian/jira # For Jira

4️⃣ Deploy Bitbucket on Bitbucket VM

On the Bitbucket VM, configure and deploy Bitbucket using Docker Compose:

version: '3'
services:
  bitbucket:
    image: atlassian/bitbucket:latest
    ports:
      - "7990:7990"
      - "7999:7999"
    environment:
      - 'JDBC_URL=jdbc:postgresql://my-postgres-db.postgres.database.azure.com:5432/bitbucket_db'
      - 'JDBC_USER=bitbucket_user'
      - 'JDBC_PASSWORD=StrongBitbucketPassword'
      - 'BITBUCKET_LFS_ENABLED=true' # Enable Git LFS
      volumes:
      - /opt/atlassian/bitbucket:/var/atlassian/application-data/bitbucket
      restart: unless-stopped
    networks:
      - atlassian
networks:
  atlassian:

5️⃣ Deploy Jira on Jira VM

On the Jira VM, configure and deploy Jira using Docker Compose:

version: '3'
services:
  jira:
    image: atlassian/jira-software:latest
    ports:
      - "8080:8080"
    environment:
      - 'JDBC_URL=jdbc:postgresql://my-postgres-db.postgres.database.azure.com:5432/jira_db'
      - 'JDBC_USER=jira_user'
      - 'JDBC_PASSWORD=StrongJiraPassword'
    volumes:
      - /opt/atlassian/jira:/var/atlassian/application-data/jira
    restart: unless-stopped
    networks:
      - atlassian
networks:
  atlassian:

6️⃣ Access Your Applications

cd /opt/atlassian
docker-compose up -d

✅ Bitbucket → http://your-azure-ip:7990

✅ Jira → http://your-azure-ip:8080

7️⃣ Secure Your Setup

Ensure that only trusted IPs can access your services by configuring firewall rules.

8️⃣ Configure Bitbucket & Jira

Go to the web interface and complete the setup:

• Enter PostgreSQL database details.
• Create admin credentials.
• For Jira, set up a new project.

9️⃣ Link Bitbucket & Jira

In Bitbucket, go to Administration → Jira Integration and add your Jira server URL.

Now, Jira issues will be linked to commits, branches, and pull requests! 🎯

✅ Done!

Your Bitbucket & Jira are now running on separate VMs with a shared PostgreSQL database on Azure! 🎉

# Initialize Git LFS
git lfs install

# Track Source Engine-specific model, texture, and map files
git lfs track "*.mdl" "*.vtx" "*.vvd" "*.phy" "*.ani" "*.dx80.vtx" "*.dx90.vtx" "*.sw.vtx" "*.xbox.vtx" \
"*.vmt" "*.vtf" "*.vmf" "*.vmm" "*.bsp" "*.nav" "*.lin" "*.ain"

# Track Source Engine scripts and config files
git lfs track "*.qc" "*.qci" "*.txt" "*.cfg" "*.res" "*.lst" "*.kv" "*.vcd" "*.fgd"

# Track general 3D model formats
git lfs track "*.obj" "*.fbx" "*.dae" "*.smd" "*.dmx" "*.blend" "*.max" "*.3ds" "*.stl" "*.lwo" "*.abc"

# Track texture, material, and shader files
git lfs track "*.tga" "*.dds" "*.png" "*.jpg" "*.jpeg" "*.bmp" "*.psd" "*.exr" "*.hdr" "*.tiff" "*.tif" "*.vmat"

# Track audio and video formats used in Source
git lfs track "*.wav" "*.mp3" "*.ogg" "*.bik" "*.mp4"

# Track compression and archives
git lfs track "*.zip" "*.rar" "*.7z" "*.tar" "*.gz" "*.bz2" "*.xz"

# Track Source tool and engine asset files
git lfs track "*.pak" "*.vpk" "*.gma" "*.cache" "*.bin"

# Track development files and scripts
git lfs track "*.sln" "*.vcproj" "*.vcxproj" "*.user" "*.props" "*.filters" "*.bat" "*.sh" "*.cmd" \
"*.patch" "*.diff" "*.cmake" "*.mak"

# Track source control and metadata files
git lfs track "*.log" "*.sdf" "*.ipch" "*.ncb"

# Verify tracked files
cat .gitattributes

# Commit the changes
git add .gitattributes
git commit -m "Enable Git LFS tracking for Source Engine development"
git push origin main

🔹 Why Do You Need a Database?

Without a database, Bitbucket and Jira cannot function because they rely on PostgreSQL to store and retrieve data dynamically.

Think of PostgreSQL as the "brain" that remembers everything—without it, your Bitbucket repositories and Jira issues wouldn't persist after a restart.

🔹 What Does the Database Do?

For Bitbucket:

• 📂 Stores Git repository metadata (not actual code, but refs, branches, PRs).
• 👤 User accounts & permissions (who has access to what).
• 📊 Pull request & commit history (reviews, comments, approvals).
• 🛠️ Project & repository settings (hooks, CI/CD settings).

For Jira:

• 📝 Stores all issues & tickets (title, description, status, comments).
• 👥 User accounts & roles (who can create/edit/assign issues).
• 📅 Sprint & workflow data (agile boards, issue tracking).
• 🔗 Integrations & automation rules (Bitbucket links, automation triggers).

🚀 Summary

sudo apt update && sudo apt install -y nginx certbot python3-certbot-nginx

sudo nano /etc/nginx/sites-available/default

server {
  listen 80;
  server_name bitbucket.yourcompany.com;
    
location / {
  proxy_pass http://127.0.0.1:7990;
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header Host $host;
  }
}
    

sudo systemctl restart nginx

sudo certbot --nginx -d bitbucket.yourcompany.com

sudo certbot --nginx -d jira.yourcompany.com

sudo systemctl enable certbot.timer