Repository navigation
ci: Publish the feast-mcp image on merge to master - #6962
Merged
ntkathole merged 1 commit intoOct 7, 2026
Merged
ntkathole merged 1 commit into
ntkathole merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
The release workflow builds feast-mcp, but master merges push feature-server, feature-transformation-server and feast-operator to quay.io/feastdev-ci without it, so there is no :develop tag to test with. Add a job that wraps the feature-server image that job just pushed. It needs that image present, so it runs after the matrix rather than inside it. Unlike the release path this base comes from Dockerfile.dev, which installs from the lockfiles and local source, so it carries mcp-server before the first release that publishes it to PyPI. Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com>
patelchaitany
force-pushed
the
ci/publish-feast-mcp-on-master
branch
from
f8a4e75 to
f79b962
Compare
October 7, 2026 11:49
jyejare
approved these changes
Oct 7, 2026
Copy link
Copy Markdown
|
⚠️ Please install the Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## master #6962 +/- ##
==========================================
+ Coverage 49.06% 49.32% +0.25%
==========================================
Files 435 443 +8
Lines 54522 55080 +558
Branches 7954 8016 +62
==========================================
+ Hits 26752 27167 +415
- Misses 25892 26030 +138
- Partials 1878 1883 +5
Continue to review full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
ntkathole
approved these changes
Oct 7, 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 this PR does / why we need it:
Follow-up to #6957, which added feast mcp and published its image from the
release workflow only. Master merges push feature-server,
feature-transformation-server and feast-operator to quay.io/feastdev-ci,
but not feast-mcp, so there is no :develop tag to test against between
releases.
This adds a build-feast-mcp-image job to master_only.yml that wraps the
feature-server image the matrix just pushed, tagging
quay.io/feastdev-ci/feast-mcp with the commit SHA and develop.
because the base image it wraps has to exist first.
feast-mcp:<sha> and feature-server:<sha> always come from the same tree.
and the working tree rather than PyPI, so this image carries mcp-server
immediately — ahead of the first release that publishes the extra to PyPI.
Before merging
quay.io/feastdev-ci/feast-mcp does not exist yet and needs to be created as
a public repository, with the same robot write permissions as
feastdev-ci/feature-server. A push to a missing repository either fails
outright, or auto-creates a private repository that nobody can pull while CI
still reports success. The same applies to quay.io/feastdev/feast-mcp for the
release workflow already on master.
Which issue(s) this PR fixes:
N/A
Checks
Testing Strategy
Verified the image builds and runs on both published architectures, using a
base built from Dockerfile.dev as this job does:
Misc