[
https://issues.apache.org/jira/browse/AMQ-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286190#comment-17286190
]
Étienne Hossack commented on AMQ-8149:
--------------------------------------
If an artifact is certified as usable, I would expect it to have been tested by
the community. The CI pipeline should run tests on this new image I would think?
Ideally having a high-level test on the docker image would help with confidence
when a new version goes to vote - (I'm thinking of this as way that could make
the release process better - because otherwise having to push the docker images
might add _more_ overhead to a release).
Also within scope of this task would be (IMO):
# Document the docker image tags (versioning scheme) esp. if different OSs
involved.
# Document the release process for how a new image is published
# Document the docker image within the activemq website both in terms of its
existence but also as a viable method for running the service.
Other considerations:
* does the dockerfile support plugin configuration easily? either within the
image or set up for ease of extension
* should ActiveMQ provide notes or thoughts on how to extend the image (i.e.
preferring no external artifacts added via COPY commands, vs. scripts which are
easy to copy and modify at build time.
Cheers!
> Create Docker Image
> -------------------
>
> Key: AMQ-8149
> URL: https://issues.apache.org/jira/browse/AMQ-8149
> Project: ActiveMQ
> Issue Type: New Feature
> Affects Versions: 5.17.0
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
>
> Create an Apache ActiveMQ docker image
> Ideas:
> [ ] jib or jkube mvn plugin
> [ ] Create a general container that supports most use cases (enable all
> protocols on default ports, etc)
> [ ] Provide artifacts for users to build customized containers
> Tasks:
> [Pending] Creation of Docker repository for ActiveMQ INFRA-21430
> [ ] Add activemq-docker module to 5.17.x
> [ ] Add dockerhub deployment to release process
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
