Revert Jenkins build migration - #235
Merged
Merged
Conversation
AayushTyagi1
approved these changes
Aug 13, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reverts the previous Jenkins-based release/build migration by moving Python (TestPyPI/PyPI) publishing and Docker image publishing back into GitHub Actions workflows.
Changes:
- Replace Jenkins-triggered TestPyPI/PyPI publishing with in-workflow
uv build+ trusted publishing (pypa/gh-action-pypi-publish). - Replace Jenkins-triggered Docker publishing with
docker/*GitHub Actions (metadata, buildx, build/push, and Hub description update). - Remove the Jenkins-based “Build Wheel” workflow and simplify release triggering to tag pushes.
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/update-mcp-registry.yml | Minor formatting/line-number-only change in the completion message step. |
| .github/workflows/test_release.yml | Replaces Jenkins TestPyPI upload flow with uv build + trusted publishing on tag push / manual dispatch. |
| .github/workflows/release.yml | Replaces Jenkins PyPI release flow with uv build + trusted publishing and GitHub Release creation. |
| .github/workflows/docker.yml | Replaces Jenkins Docker publish flow with GitHub Actions build/push via Buildx + metadata-based tagging. |
| .github/workflows/build-wheel.yml | Removes the Jenkins-driven wheel build workflow. |
Suppressed comments (2)
.github/workflows/test_release.yml:18
- For
workflow_dispatch,actions/checkoutwill default to the branch selected in the UI (oftenmain), not the version tag you intend to publish. Checking out the provided tag input makes the published artifacts match the requested release.
- name: Checkout repository
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
.github/workflows/release.yml:34
- When this workflow is run via
workflow_dispatch,softprops/action-gh-releasewon’t infer a tag fromgithub.ref(it will be a branch ref). Providetag_nameso the release is created for the intended version tag.
uses: softprops/action-gh-release@718ea10b132b3b2eba29c1007bb80653f286566b # v3.0.1
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
3
to
7
| on: | ||
| workflow_run: | ||
| workflows: ["Build Wheel"] | ||
| types: [completed] | ||
| push: | ||
| tags: | ||
| - "v[0-9]+.[0-9]+.[0-9]+*" # Match tags like v0.1.0, v1.2.3, v1.2.3-alpha.1 | ||
| workflow_dispatch: |
Comment on lines
+13
to
15
| permissions: | ||
| id-token: write # Required for trusted publishing | ||
|
|
Comment on lines
3
to
7
| on: | ||
| workflow_run: | ||
| workflows: ["Build Wheel"] | ||
| types: [completed] | ||
| push: | ||
| tags: | ||
| - "v[0-9]+.[0-9]+.[0-9]+*" # Match tags like v0.1.0, v1.2.3, v1.2.3-alpha.1 | ||
| workflow_dispatch: |
Comment on lines
+18
to
+19
| - name: Checkout repository | ||
| uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0 |
nithishr
changed the title
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.
Related Issue
Reverts issues with release scripts
Resolves:
What does this change do?
Reverts commits that migrated the build actions to Jenkins
Why is this change needed?
The Jenkins build process has some issues with the existing release process in the MCP server that we need to fix before migrating.
Evidence of Testing
Automated tests — commands run and results summary:
No code changes from RC1 build. Tests are part of the Github Action Checks
Environments tested (both are required):
Manual verification — MCP client used (Claude Desktop, Cursor, MCP Inspector, ...) and what was exercised. Screenshots or tool-call transcripts are very helpful:
Compatibility Considerations
Checklist
cb_mcp.corecontracts / managed MCP interfaces (or discussed first)