[
https://issues.apache.org/jira/browse/JAMES-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322671#comment-17322671
]
Jean Helou commented on JAMES-3565:
-----------------------------------
Here is what I had in mind when I answered on the mailing list:
* switch image creation to jib so that it becomes a part of the build and is
easier to automate in jenkins
* add a step that automatically builds the images for master in jenkins (to
make sure that it always builds correctly so we don't get stuck on the day of
the release)
* (optional or maybe only for tags) push the images to a *staging* images
repository [1] but not on docker hub,
* (only for tags) add a step with a manual trigger that retags the tag images
and pushes them to docker hub
What I mean by staging images repository is an image repository not on docker
hub, possibly hosted by apache if there is one already or to look into finding
one. this would enable having `pre-release` or even `snapshot` images for
various kind of automation while making it clear that these are unreleased
possibly unfinished products. the equivalent of the SNAPSHOT jars on maven
central.
> Publish and use apache/james docker images
> ------------------------------------------
>
> Key: JAMES-3565
> URL: https://issues.apache.org/jira/browse/JAMES-3565
> Project: James Server
> Issue Type: Task
> Components: docker
> Reporter: Benoit Tellier
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> https://www.mail-archive.com/[email protected]/msg70107.html
> {code:java}
> Hello there,
> Following the 3.6.0 release I experimented with dockerhub and pushed the
> following images:
> - apache/james:memory-3.x.x built from
> https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/memory
> - apache/james:jpa-3.x.x built from
> https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/jpa
> - apache/james:demo-3.x.x built from
> https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/provisioned
> - apache/james:cassandra-3.x.x build from
> https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/cassandra
> - apache/james:distributed-3.x.x built from
> https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/cassandra-rabbitmq
> I however do not have the rights to manage the repository, hence can't
> add a description / overview just like apache/tika repo did. I opened
> INFRA-21718 regarding this.
> 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
> [... the JIB proposition is out of scope here ...]
> {code}
> https://issues.apache.org/jira/browse/INFRA-21718
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
