Hello Wojtek

Answers inlined.

Regards,

Benoit

Le mars 17, 2023 10:09 PM, de Wojtek A couple of questions:
- how do you actually publish docker images to docker hub?
Manually upon releases. Asf releases shall be a manual process.

But as docker is a non official release artifact (licensing) my bet is that 
infringement on the asf policy should be tolerable...

 I see that
you use `buildTar` goal, which simply creates tarballs that then can be
imported to docker daemon and then pushed to remote repository;
unfortunately it doesn't support multi-platform - only `build` does,
which immediately push to remote repository (which is not ideal and
there is an issue opened in jib repository to split building and pushing)
- do you publish any "nightly" builds? master is build every day but it
doesn't seem to be published? Nightly releases are discouraged within the asf 
as it encourages the use of non released materials.

But i won-t oppose a nightly docker build if there is a consensus on it...

Using `build` goal would probably require
using different profiles for release (with image as
`apache/james:`, eg: `apache/james:jpa-latest`) and then other
which would use different tag.

Wojtek

On 17/03/2023 04:26, Benoit TELLIER wrote:
> Hi Wojtek,
>
> On my side this is a +1, contribution welcome.
>
> Please don't hesitate to open a JIRA for this and fire a PR...
> 
> --
>
>
>
> Best regards,
>
> Benoit TELLIER
>
> General manager of Linagora VIETNAM.
> Product owner for Team-Mail product.
> Chairman of the Apache James project.
>
> Mail: btell...@linagora.com
> Tel: (0033) 6 77 25 04 58 (WhatsApp, Signal)
>
>
> On Mar 17, 2023 6:47 AM, from Wojtek Hi,
> Currently, docker images are build using jib and only single platform is
> specified. Would you be open to extending it to build and publish
> multi-platform (amd64 and arm64) images?
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org







--




Reply via email to