4 ms·
I wish they would focus on other things. Things like GitLab CI's cache are unusable with most workloads, we even had builds which were faster without the cache
by oweiler 6y ago
I wish they would focus on other things. Things like GitLab CI's cache are unusable with most workloads, we even had builds which were faster without the cache than with it.
- carlosf 6y agoGitLab customer here. Sometimes I also feel like they are adding a lot of stuff instead of improving their core services. BTW I already gave up on using GitLab's native caching in favor of doing all my CI/CD with Kaniko + Multi Stage Dockerfiles I would not care about new features if they had granular billing like AWS, GCP, etc... But here I am paying for Devsecops and a lot other stuff I don't use.
- jreporter 6y agoI would love to hear more about this billing information in GitLab. Are you looking for build minutes and CPU of Runners per cloud service? What kind of questions are you typically trying to answer with that information?
- tyeager 6y agoGitLab product manager here. Would any of the cache best practices (https://docs.gitlab.com/ee/ci/caching/#good-caching-practices https://docs.gitlab.com/ee/ci/caching/#good-caching-practice...) be helpful for your use case? I'm interested to learn more about what's not working for your workloads; why cache is not improving the speed of your builds.
- jreporter 6y agoSome issues to consider following include: - https://gitlab.com/gitlab-org/gitlab/-/issues/17307 https://gitlab.com/gitlab-org/gitlab/-/issues/17307 - https://gitlab.com/gitlab-org/gitlab/-/issues/24677 https://gitlab.com/gitlab-org/gitlab/-/issues/24677 - https://gitlab.com/gitlab-org/gitlab/-/issues/18358 https://gitlab.com/gitlab-org/gitlab/-/issues/18358