pythonicshahdev/boomi-cicd-jenkins repository overview

⁠Boomi CI/CD Jenkins

A self-contained Jenkins CI/CD environment for demonstrating Boomi DevOps. This environment is pre-configured and spun up with a single docker run command, featuring two pipelines ready on first start.

⁠🛠 Features & What's Included

• Automatic Component Discovery — Finds deployable Boomi components (process, webservice.external, webservice.internal, flowservice, processroute, tpgroup, customlibrary, certificate) within a configured folder.
• Automated Packaging & Deployment — Leverages the Boomi Platform API using native Boomi component versions, always selecting the most recently created package regardless of version string format.
• Multi-Environment Pipeline — Built-in manual approval gates for secure DEV → STG → PROD promotions.
• Lint Stage — Fetches component XML from Boomi and runs XPath quality rules, archiving a report on every pipeline run.
• GitHub & Bitbucket Support — Release repo can be hosted on either platform via SSH key or HTTPS token.
• Optional SonarQube Integration — Skip by leaving credentials empty.
• Instant Readiness — Pre-configured Jenkins instance with both pipelines immediately available on first start.

⁠📋 Requirements

Before running the container, ensure you have the following:

• ACCESS_TOKEN — Contact Shah to obtain this.
• Boomi API Credentials — Account ID, username, and API token.
• Release Repo Access — SSH key or HTTPS token for your GitHub or Bitbucket release repo (see setup steps below).
• Boomi Atom — Must be attached to your target environment.

⁠🔑 Release Repo Authentication (One-Time Setup)

Choose either SSH or HTTPS depending on your preference.

⁠Option A — SSH Key (works with GitHub and Bitbucket)

ssh-keygen -t ed25519 -C "jenkins-ci" -N "" -f ~/.ssh/bitbucket_jenkins
cat ~/.ssh/bitbucket_jenkins.pub

Add the public key as a deployment key on your release repo:

• Bitbucket → Repo Settings → Access keys → Add key
• GitHub → Repo Settings → Deploy keys → Add deploy key (enable Allow write access)

⁠Option B — HTTPS Token (GitHub, simpler)

Create a GitHub Personal Access Token with repo scope at GitHub → Settings → Developer settings → Personal access tokens.

No key generation or deploy key setup required — pass the token as RELEASE_REPO_TOKEN at container startup.

⁠🚀 Quick Start

⁠Using SSH (GitHub or Bitbucket)

docker run -d --name boomi-jenkins -p 8080:8080 \
  -e ACCESS_TOKEN=<provided_token> \
  -e JENKINS_ADMIN_PASSWORD=<your_password> \
  -e BOOMI_USERNAME=<api_user_email> \
  -e BOOMI_PASSWORD=<BOOMI_TOKEN.xxx> \
  -e BOOMI_ACCOUNT_ID=<account_id> \
  -e BOOMI_FOLDER_NAME=<folder_name> \
  -e [email protected]:<username>/<repo>.git \
  -e BOOMI_ENV_DEV=<environment_name> \
  -v ~/.ssh/bitbucket_jenkins:/run/secrets/bitbucket_ssh_key:ro \
  -v jenkins_home:/var/jenkins_home \
  pythonicshahdev/boomi-cicd-jenkins:latest

⁠Using HTTPS Token (GitHub)

docker run -d --name boomi-jenkins -p 8080:8080 \
  -e ACCESS_TOKEN=<provided_token> \
  -e JENKINS_ADMIN_PASSWORD=<your_password> \
  -e BOOMI_USERNAME=<api_user_email> \
  -e BOOMI_PASSWORD=<BOOMI_TOKEN.xxx> \
  -e BOOMI_ACCOUNT_ID=<account_id> \
  -e BOOMI_FOLDER_NAME=<folder_name> \
  -e RELEASE_REPO_URL=https://github.com/<username>/<repo>.git \
  -e RELEASE_REPO_TOKEN=<github_pat> \
  -e BOOMI_ENV_DEV=<environment_name> \
  -v jenkins_home:/var/jenkins_home \
  pythonicshahdev/boomi-cicd-jenkins:latest

Jenkins will be available at http://localhost:8080 once startup completes (~60 seconds).

⁠⚙️ Environment Variables

⁠Required

⁠Release Repo Auth (one of the following)

⁠Optional

⁠🔄 Two Pipelines

Webhook (optional): http://<host>:8080/generic-webhook-trigger/invoke?token=boomi-release Supports both GitHub and Bitbucket push webhooks.

⁠⚠️ Upgrading from an Earlier Version

Wipe the volume before starting the new image:

docker rm -f boomi-jenkins
docker volume rm <your_jenkins_home_volume>
docker run ... pythonicshahdev/boomi-cicd-jenkins:latest

All configuration is baked into the image — nothing is lost by wiping the volume.

⁠🏗 Platforms

linux/amd64 · linux/arm64