Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform.
What are people migrating to? I am looking at bitbucket again I guess.
21–30 of 131 posts
Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform.
What are people migrating to? I am looking at bitbucket again I guess.
Does this mean I can ewrite a web app, put the source on GitLab and have GitLab run the web app (ideally with very minimal hassle)? If not, what does it mean? What is Gitlab letting me do now than (a) it didn't do before (b) Github doesn't do?
> Does this mean I can ewrite a web app, put the source on GitLab and have GitLab run the web app (ideally with very minimal hassle)?
Cloud Seed aims to make this easier, deploying the web application with minimal effort to your preferred cloud. More details in https://docs.gitlab.com/ee/cloud_seed/ and https://hello.cloudseed.app/ - it is a joint project from Google Cloud and GitLab.
In case you run your web app in a containerized stack, and prefer to deploy to Kubernetes, the integration with the Agent for Kubernetes has been greatly improved: https://docs.gitlab.com/ee/user/clusters/agent/
If you are looking to host static web apps (e.g. Hugo, etc.), GitLab Pages can help. More ideas in this blog post to choose a static site generator (SSG): https://about.gitlab.com/blog/2022/04/18/comparing-static-si...
> If not, what does it mean? What is Gitlab letting me do now than (a) it didn't do before (b) Github doesn't do?
Depending on which version you are at, new releases add features every month on the 22nd. GitLab 14.10 https://about.gitlab.com/releases/2022/04/22/gitlab-14-10-re... added the GitLab Runner Operator for Kubernetes for example. That's an integration after the create (SCM) and verify (CI) stage, ensuring that cloud native deployments deploy applications, and maintenance levels follow best practices. There are more stages in the DevOps lifecycle, such as package and release or protect and secure.
Observability for deployed applications, and ensuring that performance regressions do not reach production is also a very hot topic imho (shameless plug: join my talk at KubeCon EU to chat more https://kccnceu2022.sched.com/event/yttd?iframe=no :))
With regards what you can do now - I've written a blog post about my favourite hacks in GitLab a while ago, maybe there are some features or workflows that are useful for your environment: https://about.gitlab.com/blog/2021/10/19/top-10-gitlab-hacks...
That said, GitLab 15.0 is around the corner, coming May 22. https://about.gitlab.com/upcoming-releases/ I'm personally most excited about the Podman support for GitLab runner, helping with containerized CI/CD infrastructure as alternative to Docker as executor.
The GitLab direction handbook provides more insights for future plans: https://about.gitlab.com/direction/ Recommend diving into the stages and review based on your requirements, or potential new ideas and use cases. If you miss anything, please open feature proposals to collaborate: https://gitlab.com/gitlab-org/gitlab/-/issues Thanks :)
Earlier quoted context omitted.
It means that a big part Gitlab's offering is now things like CI, whereas originally it was just code hosting.
They haven't sold them selves as 'just code hosting' for some time. I almost wish they did. They've negleted basic stuff yet their marketing sells them as an all-in-one solution. A thousand dollars per seat per year (no fractions!) for the WHOLE organization just for nested Epics? No thanks. This 2 year old thread just keeps on giving: https://gitlab.com/gitlab-org/gitlab/-/issues/213185 I'd join many participants in…
What would you recommend instead? Gitea?
Old logo was probably the cleverest rendering of a fox using very few lines. The new logo is a lot less smart, much more standard. Typography is also uninspiring: seems to be using Inter, which is designed to not have any character (pun not intended). Although, to be fair, old logo also had very basic typography.
The GitLab logo/mascot is actually a tanuki, a Japanese racoon dog. It symbolizes our values as a smart animal that works in a group to achieve a common goal.
Old(er) tanuki-like logo for comparison https://gitlab.com/gitlab-com/gitlab-artwork/-/blob/9b07772f...
>DevOps Is at the Center of Gitlab Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform. What are people migrating to? I am looking at bitbucket again I guess.
>DevOps Is at the Center of Gitlab Yeah, just had a call with them and they confirmed that for only VCS its not feasible to use their platform. What are people migrating to? I am looking at bitbucket again I guess.
Depending on the size of your org, If it's small GitLab CE is free and can readily handle VCS no problem, you won't have a support contract though.
DevOps become center part of Gitlab which we don’t use and need any of those feature. We all need a code storage, code review, issue tracking and the CI/CD. We would pay advance features of those (epics, multiple assignee, etc) but we have to pay super expensive top tier which includes unnecessary DevOps stuff. We left and happy so far.
We are using Kubernetes and custom DevOps tools but don’t want to handle things the way that Gitlab does.