[
https://issues.apache.org/jira/browse/JAMES-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320981#comment-17320981
]
Juhan Aasaru commented on JAMES-3565:
-------------------------------------
I have some experience with publishing Dockerhub images for an Apache project
(apache fineract-cn-*).
After some discussions with Infra this is how it was set up eventually:
We used Dockerhub Autobuild feature:
[https://docs.docker.com/docker-hub/builds/
|https://docs.docker.com/docker-hub/builds/]
Dockerhub autobuild monitors what is happening to github repository and
triggers a build if a configured condition (new tag created, push to specific
branch) are met.
So the build is done by Dockerhub itself. The configuration also works with
regular expressions.
At start I experimented with my own dockerhub account on my fork. When I
reached the desired configuration I asked infra to set up the same
configuration on the Dockerhub for the official Apache account of that repo.
For fineract-cn there exists separate pages for each artificat. So there are:
[https://hub.docker.com/r/apache/fineract-cn-identity]
[https://hub.docker.com/r/apache/fineract-cn-provisioner]
etc.
To set up something similar for Apache James we would only need to
1) agree the conditions when to trigger a dockerhub build.
2) how to organize the images (are they all under
[https://hub.docker.com/r/apache/james] like now)
Sure we want to trigger a build every time a tag is created. And this is
basically it I think.
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.
This is what was set up for fineract-cn:
https://cwiki.apache.org/confluence/display/FINERACT/DockerHub+images
> 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]
