Implemented and pushed, it's in the orchestra repo
ACK, leaving this message here on (IMHO) how to handle the transition:...
I can add another env variable which skips cleanup...
Eh ok, I can move this file there....
I'd move this to something like .orchestra/ci/cleanup.sh which is then called after the call to .orchestra/ci/ci.sh. I think this is better because...
You're right, it's not a perfect solution....
I did look at that, and considered it with master. But then the behavior would be "different" from all the other orchestra stuff, e.g. it would not...
This list will break and go unnoticed....
In the past we considered this: https://docs.gitlab.com/ee/ci/pipelines/settings.html#specify-a-custom-cicd-configuration-file...
As we discussed, test_pipeline_id is no longer needed since the only time the hitman CI is triggered is after the regression suite has run.
Checked, there's no way to specify a .gitlab-ci.yml from the orchestra repo
I've double checked, the pipeline_create function relies on the list of changed files in the binary archives, so to make it all work it would requi...
Add a comment stating why we forward this stuff.
Can we launch the CI with a custom .gitlab-ci.yml file so that we can move this to the real orchestra?