Optimize Upgrade path test E2E run
- Dominant language
- Go
- Stars
- 353
- Forks
- 221
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
## Describe the proposal
Currently for running all the upgrade paths verification, it takes almost 25 minutes for the test suite to complete. (timeout 30mins)
The proposal here is that we only run the latest upgrade path (upgrade and downgrade) against each PR in CLI.
The full suite of upgrade paths will only be run against the master code in a scheduled run.
The issue here is, if there are changes in helm version that breaks the previous upgrade paths, that can only be caught after the code has been merged to master. But still that is a small risk to the benefit of having quicker PR check completion.
One other suggestion is make use of an `/ok-to-test` command to run the full suite of upgrade path tests as necessary in addition to the scheduled runs. That will also help mitigate this risk.
Thoughts on this? @artursouza @yaron2 @pravinpushkar @shubham1172 @ItalyPaleAle
## Release Note
RELEASE NOTE:
Contributor guide
Assessment
This issue has not been assessed yet.