clustermesh: ci: add MCS-API conformance test#44424
Conversation
0db0f1d to
39acc6f
Compare
|
/ci-mcs-api |
39acc6f to
a1a4177
Compare
|
/test |
a1a4177 to
85c82f1
Compare
|
/test |
9ea10d8 to
30f414e
Compare
|
/test |
|
@MrFreezeex thank you for the contribution! A couple of clarifications:
|
441677b to
96b9567
Compare
Sure! I added a few details in those in my last push
Not really it was the way I found to actually trigger this test as I think I can't trigger it via ariane if some combination of ariane config / workflow are not in main (I think?), I am going to drop this before merging the PR essentially as I was also saying here: #44424 (comment) |
Thank you!
Gotcha! |
|
/test |
Wire up MCS-API official conformance test in our go test infra. The approach done here is the same/is copied from the existing Gateway-API conformance test and essentially done through direct go dependency rather than building the test separately. Signed-off-by: Arthur Outhenin-Chalandre <git@mrfreezeex.fr>
Add a new workflow to trigger the MCS-API conformance test added in the previous commit. This new workflow is essentially a crossover of the existing conformance clustermesh workflow and the Gateway-API workflow (as we based the go test integration of MCS-API on the existing Gateway-API ones). This new workflow keep a matrix shape for future extensibility and remain close to the other clustermesh/gateway-api workflows. Signed-off-by: Arthur Outhenin-Chalandre <git@mrfreezeex.fr>
96b9567 to
83e7646
Compare
|
/test |
|
/test |
|
@MrFreezeex just FYI I changed the release note for this one to CI, as there's no user-facing changes here. |
Uh oh!
There was an error while loading. Please reload this page.