SONAR-21408 run static test in PR

[jCOTINEAU]

No description provided.

[carminevassallo]

Hey @jCOTINEAU is there a specific reason for running the static test in GH Actions rather than Cirrus?

[jCOTINEAU]

@carminevassallo, comfort mostly as we already had a similar behavior for next scan with our GitHub_action, so it was very quick to implement.

This is a very small baby step in my opinion.

[carminevassallo]

Given that we are trying to use one CI system, would that be better to spend a little bit more time but implement the step in Cirrus?

[carminevassallo]

Thanks for refactoring your previous change! I think we could add another small improvement that will be useful for the other tasks too. As of now, in our CI, we don't test against a specific version of k8s.

How about we add an ENV fixing the k8s version (e.g., KUBE_VERSION) that we use to execute the static tests and to create the kind cluster (in the wait_for_kind script we don't specify the k8s version)?

p.s.
I also suggest that we rename the task into "static_compatibility_test"

[sonarqube-next]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[carminevassallo]

Great job 💯