Sadly, too often GitLab is overlooked for a terrible GitHub+JIRA combo :-(
GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
31–40 of 58 posts
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#32Gitlab API is amazingly simple and flexible, can be used efficiently from the terminal to list CI jobs, your issues, edit them,.. Gitlab CI is top-notch, things like CI_COMMIT_BEFORE_SHA environment variable for monorepos is a killer feature, now npm registry, .. Gitlab wiki for documentations At work we are using Atlassian products, they would be so efficiently replaced by just Gitlab
Sadly not in situations where you need overview for more then one project. Viewing of mergerequest for all projects you have access to was disabled cause of performance problems.
Is there an issue for that? On the current version of GitLab https://gitlab.com/dashboard/merge_requests?assignee_usernam... loads in half a second https://www.dropbox.com/s/rfj1svopkexl6vb/Screenshot%202019-... and I have 1700 merge requests.
Maybe it was a regression in an old version?
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#33I've been enjoying GitLab at my last three employers now, with the CI integration being the most liberating feature compared to the traditional CI providers. Especially the Docker CI runner gives you a great integration test environment, and I'm impatiently waiting for this MR [0] that will allow dependant containers to also talk to each other. It's the last missing piece for my ideal CI setup. [0] https://gitlab.com…
GitLab product manager for Verify (CI) here.
Thanks for bringing this up I hadn't seen your contribution! I think this is a great idea. I know the technical team has been overwhelmed with community contributions as of late - which is a good problem to have but one that we're still solving. I'm going to try and shepherd this one along myself. If you want you can reach out to me on Twitter @olearycrew or my email is boleary [at] gitlab.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#34I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little too high for my taste. I wish there were ways to reduce this.
I occasionally have to rm my docker instance and recreate it. I'm not sure what it's doing, but at least it's an easy fix.
I have the same issue. Every once in a while the docker instance will get into a endless loop trying to start up and failing. So far the only fix I have found is to remove and recreate the instance. Still, I love having my own local GitLab.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#35I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little too high for my taste. I wish there were ways to reduce this.
Could you show the output of `ps aux` inside the container? Also note that GitLab Omnibus will add more Unicorn processes the more available RAM it has in the system. You can turn off that automatic scaling by lowering the number of processes via https://docs.gitlab.com/omnibus/settings/unicorn.html.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#36I like GitLab but noticed my Docker container running it is steadily requiring more memory to run smoothly. It’s sitting at 12GB right now, which is a little too high for my taste. I wish there were ways to reduce this.
One of our Engineering Fellows is working Memory Optimization across the entire product this quarter. We are aware, and starting on it!
That fellow would be Stan, the person who just commented with https://news.ycombinator.com/item?id=18972052
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#37I've been enjoying GitLab at my last three employers now, with the CI integration being the most liberating feature compared to the traditional CI providers. Especially the Docker CI runner gives you a great integration test environment, and I'm impatiently waiting for this MR [0] that will allow dependant containers to also talk to each other. It's the last missing piece for my ideal CI setup. [0] https://gitlab.com…
Edit: Saw that you are not the author of the merge request. Then thank you for highlighting it.
Oh jolly good! This exact feature was something I've thought about as useful for microservice stacks where you need interconnected background services for integration testing. Very nice of you to contribute this feature, thanks! Hopefully this will be merged at some point.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#38How well does on-premises Gitlab work? Can it run relatively maintenance-free? I heard some negative stories, but I don't know what is true. My team of devs doesn't have a dedicated sysadmin.
[deleted]
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#39I've been enjoying GitLab at my last three employers now, with the CI integration being the most liberating feature compared to the traditional CI providers. Especially the Docker CI runner gives you a great integration test environment, and I'm impatiently waiting for this MR [0] that will allow dependant containers to also talk to each other. It's the last missing piece for my ideal CI setup. [0] https://gitlab.com…
GitLab product manager for Verify (CI) here. Thanks for bringing this up I hadn't seen your contribution! I think this is a great idea. I know the technical team has been overwhelmed with community contributions as of late - which is a good problem to have but one that we're still solving. I'm going to try and shepherd this one along myself. If you want you can reach out to me on Twitter @olearycrew or my email is bo…
Great to hear you're looking into it! I do have to clarify that I'm not the owner of the MR though, not meaning to take credit of @krotscheck's work.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#40I think Gitlab is awesome. However, their current homepage hides their actual site (the repositories) and makes it hard as a developer to actually get started compared to Github. Looking through (browsing repositories) there is almost NO adoption to gitlab.
Well it seems like a very different model to Github. I don't know the figures, but the teams I encounter using Gitlab are self-hosting, you aren't going to be able to browse their (private) repos.
Depends on what we are comparing.
Gitlab Cloud v Github Cloud. Github cloud is easier to grok, and get started versus gitlab, adoption on github is very visible, and immediate from first landing.
Gitlab On Premise v Github Enterprise. Gitlab wins in offering (open source, and complete ci/cd). However, I would argue that the marketing is much stronger with Github. Github has a streamlined message which you can consume easily and then once you're in you get deeper into the meaning of.
This is what I am referring to. Model or not, it's something that is a barrier to entry.