[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010948#comment-17010948
]
Jacob Barrett commented on GEODE-7651:
--------------------------------------
To be clear, we and many ASF projects publish pre-release artifacts. Many
publish to the ASF snapshot repository, while we post to our own snapshot
repository in GCP. What is really in question here and in this LEGAL-503 JIRA
is what about the other files included in the image from the upstream
dependencies. Given that we already publish the released version on the
official ASF Docker Hub account I don't understand why a pre-release to a
pre-release image repository would be any different. The contents and
dependencies would be the same, just not blessed as a release.
> Provide docker target for geode-assembly
> ----------------------------------------
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
> Reporter: Michael Oleske
> Assignee: Michael Oleske
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
