4 ms·
Thank you for the awesome detailed feedback. Responded point by point below: > FF only merges is only EE (too bad that would be a really major selling point ev
by jobvandervoort 10y ago
Thank you for the awesome detailed feedback. Responded point by point below:
> FF only merges is only EE (too bad that would be a really major selling point even for CE, squash button would be unnecessary)
These are always hard choices to make for us. We wrote about these decisions here [0].
> CI is a little limited compared to a full blown Jenkins - We hit a CI bug which still shows up "Running" Pipelines
We're still young, but confident that we'll get there! CI/CD is a major focus for us and we're working really hard to improve it with every release. Love to get specific feature requests for things that we miss in comparison with Jenkins.
Regarding the bug: I've pinged our PM on it.
> Artifacts API is limited to everything or nothing
Could you elaborate? I know we have numerous improvements planned, but I'm not sure about their prioritization.
> 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)
Hm, could you write a feature proposal for this [1]? It sounds like a great improvement.
> No Custom CSS (yeah our logo isn't 72px x 72px...)
We're extremely hesitant to do this, as we make many changes between releases. This would break custom css with every upgrade, in turn resulting in a worse experience.
I rather hear suggestions about specific parts in the interface that should be made customizable or suggestions about changes to the UI altogether.
Although I'm not a fan of custom css, there is an issue to discuss this and I welcome your input there [2].
[0]: https://about.gitlab.com/2016/01/11/being-a-good-open-source-steward/ https://about.gitlab.com/2016/01/11/being-a-good-open-source...
[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/new https://gitlab.com/gitlab-org/gitlab-ce/issues/new
[2]: https://gitlab.com/gitlab-org/gitlab-ce/issues/15635 https://gitlab.com/gitlab-org/gitlab-ce/issues/15635
- merb 10y agoActually as already said even with the stuff mentioned here, it's really really a good project and we are happy. to [0] we've gone the CE route first since we are too small and too fast running that a EE makes sense yet (too good that you can switch between the two without any major drawbacks [http://docs.gitlab.com/ee/downgrade_ee_to_ce/README.html http://docs.gitlab.com/ee/downgrade_ee_to_ce/README.html] and [http://docs.gitlab.com/omnibus/update/README.html#from-community-edition-to-enterprise-edition http://docs.gitlab.com/omnibus/update/README.html#from-commu...] thats one of the major selling points, ease of use is really big in gitlab). but sitll every feature mentioned here wasn't in bitbucket so it's not like we've missing something, we've gained something while switching so we are probably whining on a really high level ;) Oh and thanks god for the easy backup stuff, which even works while running (which other products doesn't....)
- jobvandervoort 10y agoThanks merb!