Le mardi 11 décembre 2018 à 14:22 +0100, Carlos Soriano a écrit :
1. No Cross-Project CI support It's a bit off topic, as GStreamer is on FDO now. But the one thing that had hit was how complex the CI deployment across multiple projects (repository is). We really miss the pipeline aggregation on trigger that exist in the EE version. The side effect, builds are scattered across all repo, instead of being centrealized on the specific build system repo (in our case cerbero and gst-build). So looking over all builds is near impossible. The caches are always cold, because the build is too scattered. So all in all, what I really miss is that ability to trigger another project (repository) pipeline and gain an aggregated pipeline. With Jenkins, it fully centralized, hence much simplier, but still, now we can per commit CI, which is great. 2. No multi-commit codec review workflow Unlike github, there is no fluid way to navigate through each commits one by one during the review. The stack of commit is also upside down for a review. I generally endup opening commit in browser tabs, but that's not idea. Note that this is probably not a regression from bugzilla, but I was surprise to find out how inferior this is in gitlab in contrast to gihub.
|
Attachment:
signature.asc
Description: This is a digitally signed message part