Discuss the possibility of moving some sylva test units to CI tests

We currently have a few MR's that aim to introduce some new sylva-units just for testing another unit :

  • !3177 (merged)
  • !2912

It may make more sense to implement this on the CI side, under deployment-test step or wherever is deemed right to be, instead of having extra sylva-units .

This could also be applicable for kubevirt-test-vms perhaps.

cc: @loic.nicolle @mederic.deverdilhac @rletrocquer @tmmorin @feleouet

Summary

related references

Details

Assignee Loading
Time tracking Loading