[
https://issues.apache.org/jira/browse/JAMES-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321017#comment-17321017
]
Benoit Tellier commented on JAMES-3565:
---------------------------------------
The problem with the "tag" condition is that it would lead to not-yet-voted
releases to be exposed on dockerhub - as the maven plugin tags things itself.
It might result in users downloading potentially problematic items, if the
process is repeated several time with SHA-1 changes they might not even realize
it.
I am thus aseptically for the "tag condition".
However if there is a button I have the right to click to deploy to trigger
with my (or any other) dockerhub account the images build, then yes I want that
(at least eventually)!
I also think that integrating docker images integration to the docker build
with JIB would greatly help such automation efforts.
> One option to get more builds would be triggering tags like 3.6.1-M1 or smth
> like that - something that are not real releases but still a valid point in
> time.
https://infra.apache.org/release-distribution.html#unreleased
"must not be distributed through channels which encourage use by anyone outside
the project development community"
I think active community members should be able to perform tags on their Github
forks and build the images themselves.
> 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: 0.5h
> 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]
