Repository navigation
feat: Bitbucket module-CI (shared core + Bitbucket glue) - #21
Open
SatyendraGollaFacets wants to merge 1 commit into
Open
SatyendraGollaFacets wants to merge 1 commit into
SatyendraGollaFacets wants to merge 1 commit into
Conversation
The Bitbucket counterpart of module-ci-action (GitHub) and module-ci-gitlab. module-ci-bitbucket/run.sh is the thin Bitbucket glue: it resolves the mode, maps Bitbucket's predefined variables to the generic MC_* contract, fetches and runs the SAME shared module-ci-core.sh the other hosts run, and posts the PR preview comment — so the three hosts never drift. Bitbucket Pipelines has no remote include (unlike GitLab's `include: remote:`), so a modules repo's bitbucket-pipelines.yml can't pull a hosted template; it curls this run.sh (pinned to v1) and runs it. The control-plane wire PR flips the bootstrap's placeholder bitbucket-pipelines.yml to do exactly that. Preview (on PR) and publish (on default-branch push) are supported; cleanup-on- close is deferred (Bitbucket runs no pipeline on PR close), the same gap GitLab has. Mode-mapping dry-run verified for both modes; shellcheck clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
anujhydrabadi
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The Bitbucket counterpart of
module-ci-action(GitHub, #17) andmodule-ci-gitlab(#20). Addsmodule-ci-bitbucket/run.sh— the thin Bitbucket glue that runs the same sharedmodule-ci-core.shthe other two hosts run, so the three never drift.Why a script, not an include
GitLab consumes its template as a remote
include:. Bitbucket Pipelines has no remote include, so a modules repo'sbitbucket-pipelines.ymlcan't pull a hosted template. It insteadcurls thisrun.sh(pinned tov1) and runs it. The glue resolves the mode, maps Bitbucket's predefined vars → the genericMC_*contract, fetches + runs the core, and posts the PR preview comment.merge-base(dest, HEAD)..HEADHEAD~1..HEAD(squash-merge = 1 commit)Scope
cleanup, only the Bitbucket trigger is missing. Same gap GitLab has.Testing
shellcheckclean.base..headvia merge-base; publish →HEAD~1..HEAD).Follow-up
After merge, move the
v1tag so…/github-actions/v1/module-ci-bitbucket/run.shresolves — then the control-plane wire PR works. (Same release step the GitLab robot needed.)🤖 Generated with Claude Code