If you have specific functionality that is now only in the interface in an API we'd be glad to have a look. But it sounds like you want to replace functionality in .gitlab-ci.yml with an API, this would be hard.
Instead we would gladly word with you to make GitLab CI better so you can keep using it.
1. Single pipeline => I understand using a monorepo. But I don't understand yet why you need multiple pipelines. Does the pipeline work different depending on what file is updated?
3. Do you mean setting criteria for build skipping in .gitlab-ci.yml ? What would be an example criteria?
Since you are a paying customer feel free to work with our support team to have the features you need prioritized. We want everyone to be able to use GitLab CI.
Instead we would gladly word with you to make GitLab CI better so you can keep using it.
1. Single pipeline => I understand using a monorepo. But I don't understand yet why you need multiple pipelines. Does the pipeline work different depending on what file is updated?
2. Do you mean cross project pipelines? https://gitlab.com/gitlab-org/gitlab-ee/issues/933
3. Do you mean setting criteria for build skipping in .gitlab-ci.yml ? What would be an example criteria?
Since you are a paying customer feel free to work with our support team to have the features you need prioritized. We want everyone to be able to use GitLab CI.