Add a workflow to publish images to ACR - #12
Merged
Merged
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The new Publish workflow references non-existent action versions and has reliability issues (concurrency/tag regression risk and missing Buildx setup in jobs that invoke docker buildx).
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds an automated container image publishing pipeline for the OpenOps MCP HTTP-transport image, targeting Azure Container Registry (private on main pushes and public on releases), and updates CI/documentation accordingly.
Changes:
- Introduces a new
PublishGitHub Actions workflow to build/push multi-arch images and to promote release images from private to public ACR. - Updates CI to skip the Docker image build job on push events (to avoid redundant builds on
main). - Documents the published image locations and tags in the README.
File summaries
| File | Description |
|---|---|
| README.md | Documents where main and release images are published and how they’re tagged. |
| .github/workflows/publish.yml | New workflow to build multi-arch images on main/manual runs and promote images on releases. |
| .github/workflows/ci.yml | Skips the image build job on push events to avoid duplicating Publish workflow builds. |
Review details
Suppressed comments (1)
.github/workflows/publish.yml:130
- This job calls
docker buildx imagetools create, but doesn’t set up Buildx in the job. Adddocker/setup-buildx-actionbefore the promotion step so the command works reliably across runner images.
- name: ACR login
run: |
az acr login --name openops
az acr login --name openopspublic
- name: Promote image to the public registry
- Files reviewed: 3/3 changed files
- Comments generated: 2
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
MarceloRGonc
reviewed
Sep 2, 2026
MarceloRGonc
reviewed
Sep 2, 2026
MarceloRGonc
reviewed
Sep 2, 2026
ravikiranvm
marked this pull request as draft
September 3, 2026 07:45
ravikiranvm
marked this pull request as ready for review
September 3, 2026 12:31
MarceloRGonc
approved these changes
Sep 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.
Fixes OPS-4769
Adds a github action that triggers on pushes to main and a new release
It can be run manually
Follows the same approach as in OpenOps
Tagging convention on main, release and branch
Images build on AMD64 and ARM64 architectures
A single manifest per tag
We don't rebuild images on release, we promote the latest commit's image to a public one
Merges to main and manual triggers push images to private registry. Release would push image to public registry.
Modifies the CI build job to not run on pushes to main to avoid unnecessary builds since pushes to main triggers this build and push workflow.
Note: We will require
Container Registry Repository Writerpermission on public and private registries to the existing github actions service principal.