So I think the feature we'd want to make that easier is an actual global code search API!
We do not have immediate plans to ship that yet, but I pinged our product team member there. However we do have plans to ship multi-project pipeline with an "inversion of control".
You will be able to specify pipeline relation with an upstream project, and when someone pushes a commit to it, a downstream pipeline is going to be trigger automatically. See an issue about cross-project dependencies - https://gitlab.com/gitlab-org/gitlab-ee/issues/1681!
I wrote an issue for it here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29347
This is actually a brilliant insight. I'd never thought of it that way. And I'm a one-eyed raving Concourse fan.
The best CI is the one where you write code to build/deploy etc.
Wrangling with some moronic UI exposed by the CI product to abstract code is simply wrong. Don't do CI/CD like this.
That lets teams share Concourse task and resource definitions. Many teams (including mine) publish our pipeline definitions too [0]. This enables "tooling" type teams build components that get a lot of re-use by other teams.
disclaimer: I work for Pivotal.
[0] e.g. code.cloudfoundry.org/cf-networking-ci
But I think there's a difference between a mostly complete CI product with API extension points, and a "batteries not included" CI toolbox.
Perhaps ironically, we ended up doing some development around the edges of the CI product we ultimately selected (GitLab).