Use of CI/CD pipelines
It would be a huge help to rapporteurs if we were able to use the CI/CD pipelines to validate MR/CRs before the meeting considered them.
I have lost count of the hours we have wasted fixing broken or incomplete CRs (including my own!!) after the meeting had already agreed them. More than once we have published broken specifications. The CI/CD pipelines has the potential to massively reduce this burden, streamline the meetings and make the deliverables more robust and correct.
-
How well does the ETSI forge support this?
-
Does (or should) the documentation give any guidance on creating CI/CD pipelines for testing machine-readable deliverables?
-
I believe that Gitlab.com offers free shared Runners for CI/CD. Is there any way to use these on the ETSI forge? Alternatively, does (or could) ETSI provide any infrastructure for providing the necessary Runners (e.g. a Docker or Kubernetes instance)?