search

metal3-io / project-infra

Metal3 testing infrastructure configuration
https://prow.apps.test.metal3.io
Apache License 2.0
17 stars 20 forks source link

Discrepancy between Jenkins pipelines and Prow's Config #837

Closed NymanRobin closed 3 months ago

NymanRobin commented 3 months ago

There is a discrepancy between Jenkins pipeline configs and the Prow config, the root cause of this was that the decision to only keep the latest upgrade for each branch. However, the Prow config was never updated to reflect this.

Further none of the configs for branch release-1.7 does match the actual config that exists. We should check all the Prow configs and make them reflect the tests in Jenkins

NymanRobin commented 3 months ago

/assign

metal3-io-bot commented 3 months ago

This issue is currently awaiting triage. If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance. The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
tuminoid commented 3 months ago

Can you be more specific what exactly does not match?

NymanRobin commented 3 months ago

I think it is already dealt with in the PR #838 But basically the names of the Prow triggers of the upgrade tests did not match the Jenkins pipeline jobs and thus no test were ran. Happened for example in this PR #776

tuminoid commented 3 months ago

Yeah the PR makes it clear now, thanks for the update and the fix.