Skip to content

Add GitHub Actions workflow for automated Docker image builds#1

Closed
rajpratik71 wants to merge 1 commit intoopendata-oss:masterfrom
rajpratik71:feat/ghcr-docker-build-support
Closed

Add GitHub Actions workflow for automated Docker image builds#1
rajpratik71 wants to merge 1 commit intoopendata-oss:masterfrom
rajpratik71:feat/ghcr-docker-build-support

Conversation

@rajpratik71
Copy link

Implements CI/CD pipeline to build and push Docker images to GitHub Container Registry on push to master, tag creation, and pull requests. Uses docker/Dockerfile.build with caching and automatic tag generation based on branch, PR, semver, and commit SHA.

Implements CI/CD pipeline to build and push Docker images to GitHub Container Registry on push to master, tag creation, and pull requests. Uses docker/Dockerfile.build with caching and automatic tag generation based on branch, PR, semver, and commit SHA

Signed-off-by: Pratik Raj <rajpratik71@gmail.com>
@rajpratik71 rajpratik71 force-pushed the feat/ghcr-docker-build-support branch from 72f0212 to d732688 Compare March 5, 2026 11:47
@rajpratik71
Copy link
Author

Successful execution of workflow happened at Performance-Eng#1

@rajpratik71
Copy link
Author

rajpratik71 commented Mar 6, 2026

@hachikuji for review

@hachikuji
Copy link
Collaborator

Thanks for the patch! It looks like you did a similar patch upstream openmessaging#450. Once that is checked in, we can merge it here. This fork is focused on the opendata driver which we hope to push upstream once it is stable. We're unlikely to push docker images directly from here.

@hachikuji hachikuji closed this Mar 6, 2026
@rajpratik71
Copy link
Author

Thanks for the patch! It looks like you did a similar patch upstream openmessaging#450. Once that is checked in, we can merge it here. This fork is focused on the opendata driver which we hope to push upstream once it is stable. We're unlikely to push docker images directly from here.

Sure, let's see. I see very less activity in the upstream and seen this fork is actively developed , so raised it here also.

@rajpratik71
Copy link
Author

Thanks for the patch! It looks like you did a similar patch upstream openmessaging#450. Once that is checked in, we can merge it here. This fork is focused on the opendata driver which we hope to push upstream once it is stable. We're unlikely to push docker images directly from here.

@hachikuji looks like there is no activity or update on openmessaging#450 PR and overall project itself.

So, are you guys looking to maintain this fork as active fork ?

If yes, can you please re-open and merge this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants