3 ms·

Cool to hear you selected GitLab. We recently added multi project pipeline visualization. That was partially inspired by concourse CI. Is there anything else yo

by sytse 9y ago

Cool to hear you selected GitLab. We recently added multi project pipeline visualization. That was partially inspired by concourse CI. Is there anything else you would like to see?

witten 9y ago
Interesting you should mention that. Right around the time you implemented multi-project pipeline visualization, we built a bot that listens for GitLab build completion events, hits the (undocumented /unsupported) internal GitLab global code search ElasticSearch index, finds downstream dependencies of the completed build (as declared in setup.py/package.json), and triggers their builds as well.. Taking full advantage of your nifty visualization. So I think the feature we'd want to make that easier is an actual global code search API!
- sytse 9y ago
  Cool! I think we're building this into GitLab itself. I'll ask the CI CD team to comment.
- grzesiekb 9y ago
  Thanks for this proposal! It might be a cool feature indeed. I created an issue about it in our issue tracker, see https://gitlab.com/gitlab-org/gitlab-ce/issues/35186 https://gitlab.com/gitlab-org/gitlab-ce/issues/35186. 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 https://gitlab.com/gitlab-org/gitlab-ee/issues/1681!
  - witten 9y ago
    Awesome, thanks for filing!
gaff33 9y ago
Please can you allow for any acyclic graph rather than the current stage system? This would allow us to have our long running integration tests run in parallel with shorter tasks! I wrote an issue for it here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29347 https://gitlab.com/gitlab-org/gitlab-ce/issues/29347

by sytse 9y ago

Cool to hear you selected GitLab. We recently added multi project pipeline visualization. That was partially inspired by concourse CI. Is there anything else you would like to see?

witten 9y ago

Interesting you should mention that. Right around the time you implemented multi-project pipeline visualization, we built a bot that listens for GitLab build completion events, hits the (undocumented /unsupported) internal GitLab global code search ElasticSearch index, finds downstream dependencies of the completed build (as declared in setup.py/package.json), and triggers their builds as well.. Taking full advantage of your nifty visualization. So I think the feature we'd want to make that easier is an actual global code search API!

sytse 9y ago
Cool! I think we're building this into GitLab itself. I'll ask the CI CD team to comment.
grzesiekb 9y ago
Thanks for this proposal! It might be a cool feature indeed. I created an issue about it in our issue tracker, see https://gitlab.com/gitlab-org/gitlab-ce/issues/35186 https://gitlab.com/gitlab-org/gitlab-ce/issues/35186. 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 https://gitlab.com/gitlab-org/gitlab-ee/issues/1681!
- witten 9y ago
  Awesome, thanks for filing!

gaff33 9y ago

Please can you allow for any acyclic graph rather than the current stage system? This would allow us to have our long running integration tests run in parallel with shorter tasks! I wrote an issue for it here: https://gitlab.com/gitlab-org/gitlab-ce/issues/29347 https://gitlab.com/gitlab-org/gitlab-ce/issues/29347