-
Notifications
You must be signed in to change notification settings - Fork 1
Containerization #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Containerization #7
Conversation
12c64b0 to
848a679
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #7 +/- ##
=======================================
Coverage 98.52% 98.52%
=======================================
Files 2 2
Lines 541 541
=======================================
Hits 533 533
Misses 8 8 ☔ View full report in Codecov by Sentry. |
|
Converting this PR to a draft while I rebase it on #8. |
This is really cool... Pbench is feeling envious ... |
Yeah, but Pbench has way more code and already has a solution (although...well...it could be made better). Seriously, though, I think I had a reason for not proposing this solution for Pbench, although I don't recall now what it was. 😵 |
848a679 to
f6c80ba
Compare
04f6c22 to
dcdac7e
Compare
|
OK, I think this is now, once again, actually, ready for review (I've left the penultimate commit unchanged and added updates in the commit that follows it for the change in the directory structure from #8, the removal of the |
dcdac7e to
2d0654d
Compare
This PR adds the capability to build and publish the
file-relayutility as a container image.This change provides a
Dockerfilewhich builds a container image that executes thefile-relayutility as its entry point. The resulting container can be invoked as though it were thefile-relayutility, withfile-relaycommand options specified at the end of the invocation command line.This change also provides a
.dockerignorefile and a GitHub Actions workflow which causes the container image to built when a commit is pushed to arelease/**branch, when a tag is created or updated, or when a GitHub release is created or updated. On successful build, the container image is exported to Quay.io and tagged with the branch name, Git tag, or release tag, as appropriate.Note that this PR is based on #10, so the commits from that PR and its precursors will show up here until they are merged.
PBENCH-1258