CTA CI pipeline triggered by EOS can not test against latest CTA tag in case of bugs/changes in pipeline code
Anytime EOS tags a new release it triggers 2 CTA CI pipelines modifying the versionlock to the tagged EOS release to run the test against it.
In case the CI pipeline code changes in the meantime and we break this functionality, we will have to currently commit a fix to the main CTA branch. This will allow us to trigger the test against main branch, but not against the latest CTA release, where this fix can not be present.
What would be the benefits of separating out git CI code from the rest of the CTA code base so that we can make fixes and modification to our deployments without touching the main CTA code repository ?