4 ms·

> - CI is a little limited compared to a full blown Jenkins - We hit a CI bug which still shows up "Running" Pipelines Do you have more examples of workflows w

> - CI is a little limited compared to a full blown Jenkins - We hit a CI bug which still shows up "Running" Pipelines Do you have more examples of workflows we are not supporting at all or well enough? > - Artifacts API is limited to everything or nothing Right you are, you might want to track this issue[1]. > - CI Stages can be defined as trigger only but you can't have multiple triggers that starting different things (considering a production trigger and a testing trigger while you don't want the 'manual' thing directly in GitLab, especially when integrating into other systems makes this a flaw) I don't fully comprehend what you mean, could you elaborate? [1] https://gitlab.com/gitlab-org/gitlab-ce/issues/20603 https://gitlab.com/gitlab-org/gitlab-ce/issues/20603

merb 10y ago
Not supported Workflows: - JUnit XML or similar output reading to have a nice output what's broken / worked - Checkstyle output / pylint / tools for other languages - What I said about Artifacts - Artifacts are hard to Track I already wrote into [1] which would also be a good way - Actually external Triggers can't be conditional: https://gitlab.com/gitlab-org/gitlab-ce/issues/19826 https://gitlab.com/gitlab-org/gitlab-ce/issues/19826 So either that or have a way to name triggers which I opened here: https://gitlab.com/gitlab-org/gitlab-ce/issues/20574 https://gitlab.com/gitlab-org/gitlab-ce/issues/20574 And I guess these are the things my company does / did with jenkins. There is also another downside but we don't do that anymore: You can't push from CI to master branches, some people do tag and create builds with their CI / CD (which we also did) but now we just push a Tag to the Repo and the CI will be: '- only: tags' and catch that up. That's all stuff I can think of now which is probably not supported by most "simple" CI / CD Tools. I guess only the big one's have such a thing like TeamCity, Jenkins and Bamboo.

merb 10y ago

Not supported Workflows: - JUnit XML or similar output reading to have a nice output what's broken / worked - Checkstyle output / pylint / tools for other languages - What I said about Artifacts - Artifacts are hard to Track I already wrote into [1] which would also be a good way - Actually external Triggers can't be conditional: https://gitlab.com/gitlab-org/gitlab-ce/issues/19826 https://gitlab.com/gitlab-org/gitlab-ce/issues/19826 So either that or have a way to name triggers which I opened here: https://gitlab.com/gitlab-org/gitlab-ce/issues/20574 https://gitlab.com/gitlab-org/gitlab-ce/issues/20574 And I guess these are the things my company does / did with jenkins. There is also another downside but we don't do that anymore: You can't push from CI to master branches, some people do tag and create builds with their CI / CD (which we also did) but now we just push a Tag to the Repo and the CI will be: '- only: tags' and catch that up. That's all stuff I can think of now which is probably not supported by most "simple" CI / CD Tools. I guess only the big one's have such a thing like TeamCity, Jenkins and Bamboo.