Consider removing Docker context generator

If you continue to use jibExportDockerContext or jib:exportDockerContext, thumbs up this issue and/or leave a comment describing your use case.

With the addition of Jib’s build to docker daemon/build tarball functions, the docker context generator is becoming less and less useful, while it becomes more of a pain to maintain as we add new features (some of which are difficult to make compatible with Dockerfiles). If this isn’t a popular feature, it may be best to remove it.

[axiopisty]

It’s unfortunate I didn’t see this ticket before the goal was removed. Our organization is using Pipeline Jenkins builds. Access to uploading/installing new docker images into the image repository is restricted to a proprietary corporate artifact as part of the build. My project currently uses the exportDockerContext goal, and then the location of that context is passed to our corporate artifact which then builds and publishes the image to the corporate repository.

As far as I am aware, I can’t upgrade to 1.0.0 without this goal.

What are the reasons (value add) to removing the goal? Is it possible to get it back?

[briandealwis]

@liqweed just to be clear, Jib is docker-less: it constructs images itself. Jib never invokes docker.

It looks like codefresh.io provides much of the useful metadata you describe as environment variables, and you could configure Jib in your pom/buildscript and to create corresponding labels with those values. And it looks like they provide a container registry at r.cfcr.io; providing they have a docker config for obtaining credentials, then Jib should should be able to push there directly.