YETUS-683 proposes to start publishing convenience binaries as images
at hub.docker.com. Included with that JIRA is a patch that provides some
(admittedly sparse) documentation on how to take advantage of those images.
My current design is to provide two images:
apache/yetus-base:(latest|branch|release tag) - Apache Yetus’
requirements in it
apache/yetus:(latest|branch|release tag) - base+ Apache Yetus
pre-installed in /usr
We’d take advantage of docker hub’s capabilities to auto-build for us
so it shouldn’t require much work other than telling infra to turn it on. The
necessary magic for hub.docker.com to build things sanely (e.g.,
apache/yetus:0.9.0 will use apache/yetus-base:0.9.0 and not latest) was already
committed as part of YETUS-15.
IMHO, I view making these images available as an absolutely critical
part of making Apache Yetus easier to use. In particular, it should be noted
that in order to make Circle CI and Gitlab CI first class citizens (see
YETUS-681), Docker images are pretty much required.
Any questions/comments/concerns?
Thanks!
