This approach keeps Vester and its dependencies happily in their Docker container, making it easy for me to run this as part of a Jenkins pipeline.
What about a pull request?
Since I am actually using my working dockerized branch, I pulled in a handful of additional tests that have yet to be merged to this main repository. I figure it would make sense to resolve those first, then the PR should only include dockerizing specific changes. But if there is a better way, let me know!
There are about three issues with running Vester in a Docker container:
I've addressed these three issues in the following ways:
The code changes are available in my working branch https://github.com/jeffgreenca/vester/tree/feature/dockerized.
Why?!
This approach keeps Vester and its dependencies happily in their Docker container, making it easy for me to run this as part of a Jenkins pipeline.
What about a pull request?
Since I am actually using my working dockerized branch, I pulled in a handful of additional tests that have yet to be merged to this main repository. I figure it would make sense to resolve those first, then the PR should only include dockerizing specific changes. But if there is a better way, let me know!