kubevirt / hyperconverged-cluster-operator / 1887
69%
main: 76%

LAST BUILD BRANCH: bump_CDI_v1.999.0-test.0_main
DEFAULT BRANCH: main
Ran
Jobs 1
Files 1
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 73.321%. Remained the same
1887

push

travis-ci-com

web-flow 
Improve upgrade test suite (#482)

Up to now, the upgrade test lane on CI was testing the upgrade, via OLM,
using a locally built registry image, which already contains a bundle (CSV+CRDs)
from the PR content, as the baseline for the upgrade.
That bundle is pointing to an already available HCO image from quay.io
( quay.io/kubevirt/hyperconverged-cluster-operator:latest ) but everything else comes
from the open PR.
The upgrade suite was going to upgrade from there to a second
locally built registry image which is exactly equal to the first one but it
point to a locally built HCO image with the code from the PR.

This approach was wrong because:
- nothing ensures that the HCO image already available on quay.io
can be successfully used with the bundle (CRDs + CSV) contained in the
PR and so with the locally built pre-upgrade registry image
- nothing tries to upgrade the dependent components from what is tracked
in an already available bundle shipped in the past to the content of the current PR
(we were testing only quay.io/kubevirt/hyperconverged-cluster-operator:latest -> `HCO from current PR`
ignoring other components that can be included with the PR).

A better approach is to start the upgrade from:
- an HCO image built in the past and shipped in quay.io
- a registry image built in the past and shipped in quay.io

In that way we can ensure that we are able to correctly
upgrade from the latest images shipped in the past on quay.io to the content
of the current PR including dependent components.

So, in this PR:
- rename the registry image from hco-registry to hco-container-registry to better describe its content (keeping hco-registry-upgrade for the upgrade registry because it's hardcoded in prow job)
- start the upgrade from quay.io/kubevirt/hco-container-registry:latest as shipped in quay.io
- significatively raise various upgrade timeouts because now we are going to test a real upgrade potentially involving also other d... (continued)

786 of 1072 relevant lines covered (73.32%)

3.43 hits per line

Jobs
ID Job ID Ran Files Coverage
1 1887.1 0
73.32
 Travis Job 1887.1
Source Files on build 1887
Detailed source file information is not available for this build.