[ 
https://issues.apache.org/jira/browse/RANGER-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Kumar resolved RANGER-5126.
------------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Merged in master: 
https://github.com/apache/ranger/commit/aeda5d4f3aafddeef403e12e4ef6c5924fb1e31b
 

This also enables the upgrades to be run for ranger-2.8 branch by default, 
cherry-pick is not required.

> CI: Add coverage for testing ranger upgrades
> --------------------------------------------
>
>                 Key: RANGER-5126
>                 URL: https://issues.apache.org/jira/browse/RANGER-5126
>             Project: Ranger
>          Issue Type: Improvement
>          Components: docker, Ranger
>            Reporter: Abhishek Kumar
>            Assignee: Abhishek Kumar
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Add a GitHub Actions workflow to test ranger upgrades from prior releases to 
> the latest release. This will be useful in validating upgrades during release 
> activities.
>  
> Scope:
>  * test upgrades with these ranger databases: postgres, mysql, oracle.
>  * test with at-least 2 prior releases to the latest release being tested for 
> upgrade.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to