Skip ITs on release branches

[see-quick]

Type of change

• Task

Description

This PR adds a condition where to run ITs. Currently we run it also on release branches but that would fail because such images are not present (GAs ones) as we are doing release candidates.

We can't run ITs in the release-* branches as we build images in separate repository.

Checklist

• Update documentation
• Update CHANGELOG.md (if present)
• Reference relevant issue(s) and close them after merging
• Write tests
• Make sure all tests pass
• Try your changes inside a Kubernetes cluster, not just from unit tests
• AI assistance was used to create this PR

[scholzj]

Doens't that suggest some issue in the build that should be fixed rather then skip the ITs?

[see-quick]

Doens't that suggest some issue in the build that should be fixed rather then skip the ITs?

No, because when you run integration tests it would try to run tests with using 0.116.0 images (which are not present yet), as there are only 0.116.0-rc1. The build with ITs will be run in the release job with replaced images (i.e., using 0.116.0-rc1).

[scholzj]

Doens't that suggest some issue in the build that should be fixed rather then skip the ITs?

No, because when you run integration tests it would try to run tests with using 0.116.0 images (which are not present yet), as there are only 0.116.0-rc1. The build with ITs will be run in the release job with replaced images (i.e., using 0.116.0-rc1).

Hmm, I guess that is an interesting issue with this 2 repositories approach 🤔

[see-quick]

Do you have anything more to this @scholzj?