Hello Jean, Answer inlined...
Le 15/04/2021 à 19:01, Jean Helou a écrit : >> Following the 3.6.0 release I experimented with dockerhub and pushed the >> following images: >> > THANK YOU ! (yes with caps because that's how grateful I am !) > > I also propose to timely edit the existing configuration to: >> - No longer use linagora repository for Apache James docker images >> distribution >> > - Only rely on released docker images (no longer branch master) to >> better fit in Apache release policies >> > I saw the corresponding PR :+1: > > >> To be fairly honest building these images took me too much time. I would >> highly appreciate automation of docker images construction as part of >> the maven build. A way to do it is JIB. [1] > > That's what I used to build my pure SMTP relay server assembly, it's being > polished but jib works great :) > > demonstrate building a james >> server image variation for a tierce project so I propose to do something >> similar, except without requiring a docker daemon. It includes CLI, >> glowroot, etc... We had been using this JIB generated image on >> production without problems. I propose we target something similar for >> James docker image generation. As part of the release process we would >> then need to load, then push the maven build results. This would lead to >> the removal of /dockerfiles folder (more or less). >> > Since docker images are not considered release artifacts under apache > policy (if I understand correctly) would it make sense to try and fully > automate the image building post release ? > add a piece to the jenkinsfile that monitors only tags, and builds the jib > image downloading the artifacts from maven central This argument make sense. Maybe we could push automatically RCs to docker hub automatically upon tagging (before the voting process), then once the vote pass just rename the images? That way: - It is automatic and convenient - We make it clear the artifact is not to be used yet This would look like what Juhan proposed in https://issues.apache.org/jira/browse/JAMES-3565 ... Thoughts? Cheers, Benoit > > >> [1] >> >> https://github.com/linagora/openpaas-james/tree/master/openpaas-james/apps/memory >> README and pom.xml are of interest. >> >> Cheers, >> >> Benoit >> >> Le 11/12/2020 à 16:29, Tellier Benoit a écrit : >>> You're right, >>> >>> I did not follow up on this. >>> >>> I just created the INFRA ticket. >>> https://issues.apache.org/jira/browse/INFRA-21180 >>> >>> As far as I understand, this is not an official release channel but >>> rather a convenience one. >>> >>> Cheers, >>> >>> Benoit >>> >>> Le 11/12/2020 à 15:18, Jean Helou a écrit : >>>>> I propose to ask for rights on apache/james repository >>>> I'm revisiting this thread after seeing >>>> https://www.docker.com/blog/supporting-open-source-projects-at-docker >> which >>>> reminded me of this effort and I was wondering if an INFRA ticket has >> been >>>> opened for james (of if there is a trace of the progress somewhere) >>>> I'm not sur exactly how the program works but if it whitelists prefixes, >>>> Apache is most likely already in it however in light of the work on CI >>>> builds on apache infrastructure, I am wondering if/how the credentials >> for >>>> pushing form CI can be setup and I was hoping to drop a comment on the >>>> corresponding ticket. >>>> >>>> jean >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org >>> For additional commands, e-mail: server-dev-h...@james.apache.org >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org >> For additional commands, e-mail: server-dev-h...@james.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
