[
https://issues.apache.org/jira/browse/RANGER-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-5506.
------------------------------------
Fix Version/s: 2.8.1
Resolution: Fixed
Merged in main (apache/ranger-tools):
[http://github.com/apache/ranger-tools/commit/a1d788028cc7520f10f25889990d34a668996a5f]
[https://github.com/apache/ranger-tools/commit/7b7451dd2239ea7870e6629cb5c6f2ca0035ba96]
[https://github.com/apache/ranger-tools/commit/834d1bbbc60c5c7d35f0930e5ca1d287f99a1fbf]
[https://github.com/apache/ranger-tools/commit/0dd64756b1f5eff8f31c36d4c5506369e23385b3]
https://github.com/apache/ranger-tools/commit/3f77e227816579acfd872365ee09237c9b10e70d
> Support Ranger Docker Image Releases from apache/ranger-tools
> -------------------------------------------------------------
>
> Key: RANGER-5506
> URL: https://issues.apache.org/jira/browse/RANGER-5506
> Project: Ranger
> Issue Type: Improvement
> Components: docker
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 2.8.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently, docker images including ranger, ranger-solr, ranger-db and
> ranger-zk are published to DockerHub and GitHub Container Registry with every
> Ranger release.
> The process of publishing images to the above registries for a Ranger release
> is currently manual and is driven from dev-support/ranger-docker.
> It would be helpful to drive the release of the ranger-docker images from a
> apache/ranger-tools and de-couple it from the development of ranger images in
> dev-support/ranger-docker for better release management.
>
> Also, add a GitHub Actions Workflow for automated build and publishing of
> images to the 2 registries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
