2 ms·
Not supported Workflows: - JUnit XML or similar output reading to have a nice output what's broken / worked - Checkstyle output / pylint / tools for other langu
by 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.