Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

about.gitlab.com

Post reply on HN
Print view View original

41–50 of 58 posts

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#41

Post by unilynx »

meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

It's on docker, gitlab/gitlab-ce:latest

We're upgrading two or three times a month, and I don't remember having had any issue just letting it update itself for at least a year.

Gitlab's downtime when upgrading the docker image is about 1 - 3 minutes every time, which hasn't been an issue for us (and otherwise I'd just schedule it for midnight)

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#43

Post by BossingAround »

meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

Well, I was able to deploy it on my home "server" within like half an hour. Migration when having hundreds of repos might be a bit more difficult, not sure about that of course.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#44

Post by boleary-gl »

baaym wrote: post #39
boleary-gl wrote: post #33

Earlier quoted context omitted.

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.

Ah sorry, my bad - I may have misread as well. Either way thanks for bringing it to my attention as I think this is a change that could make some other iterations "possible."

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#45

Post by emilycook »

graphememes wrote: post #40
allover wrote: post #28

Earlier quoted context omitted.

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…

(GitLab employee) What would you say GitHub does that makes it easier to get started on/adopt? I don't disagree, barriers to entry are just subjective so I'd like to hear your take

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#46

Post by graphememes »

emilycook wrote: post #45
graphememes wrote: post #40

Earlier quoted context omitted.

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…

(GitLab employee) What would you say GitHub does that makes it easier to get started on/adopt? I don't disagree, barriers to entry are just subjective so I'd like to hear your take

Homepage Messaging:

Github:

1. Straight to the point. For developers. Host code, work alongside millions of developers or your team. 2. Registration form right next to message. Immediate start. No need to think about much else. Let's get started. 3. Let me check their features (just in case) keep scrolling 4. Oh wow okay, woah another register form right here easy.

Gitlab:

1. Message makes me think. "A full DevOps tool~chain~.*" Why the asterisk? I'm already distracted. 2. Okay, I can manage projects, sourcecode management, CI/CD, great. 3. Get started for free... 4. Immediately see "try x for y days"... thinking "so is this paid?" 5. Look down and see I don't need to do that.

I have to do more thought now, why not just let me register from the homepage and auto-subscribe me to the gold plan and let me know that, you don't require a credit card either way.

---

This is purely from the Cloud perspective, but there is much more thinking required for Gitlab than Github.

---

Mind dump of subjectivity:

For hosted / feature-set, the way github illustrates their feature offering is much better than the table on the gitlab homepage as well. It's more about how much time do I have to vet a product. For someone who is purchasing enterprise they are more likely to invest more time, but overhead or information overload or time to trial is a real thing and can be quantified.

---

As a note, I like gitlab, the product is great, the marketing could use some work is all. Everyone there does a great job.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#47

Post by emilycook »

graphememes wrote: post #46
emilycook wrote: post #45

Earlier quoted context omitted.

(GitLab employee) What would you say GitHub does that makes it easier to get started on/adopt? I don't disagree, barriers to entry are just subjective so I'd like to hear your take

Homepage Messaging: Github: 1. Straight to the point. For developers. Host code, work alongside millions of developers or your team. 2. Registration form right next to message. Immediate start. No need to think about much else. Let's get started. 3. Let me check their features (just in case) keep scrolling 4. Oh wow okay, woah another register form right here easy. Gitlab: 1. Message makes me think. "A full DevOps to…

Thank you! That was really helpful. Sometimes you just get so familiar with something that you lose focus on what it's like to view it for the first time, I'll pass along your feedback

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#48

Post by meddlepal »

lbotos wrote: post #16
meddlepal wrote: post #14

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

It's a lot easier, and dead simple to run a small single server install. When you start scaling, it gets a little harder, but our vision it to leverage K8s for that type of deployment. (Source: work at GitLab, and I wouldn't If we had to manage the infra by hand vs. omnibus/k8s)

Any comment on how well the single server install scales before needing to invest in the more complex HA solution?

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#49

Post by sytse »

graphememes wrote: post #46
emilycook wrote: post #45

Earlier quoted context omitted.

(GitLab employee) What would you say GitHub does that makes it easier to get started on/adopt? I don't disagree, barriers to entry are just subjective so I'd like to hear your take

Homepage Messaging: Github: 1. Straight to the point. For developers. Host code, work alongside millions of developers or your team. 2. Registration form right next to message. Immediate start. No need to think about much else. Let's get started. 3. Let me check their features (just in case) keep scrolling 4. Oh wow okay, woah another register form right here easy. Gitlab: 1. Message makes me think. "A full DevOps to…

Thanks for the feedback! I love the point about getting out of the way and starting on a gold plan. I'll discuss with our CMO.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#50

Post by shinya »

sebazzz wrote: post #7

How 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.

It's basically maintenance-free, and if you got trouble, you can ask in Issue Tracker https://gitlab.com/gitlab-org/gitlab-ce/issues. We can advise how you can recover your instance case-by-case. (Also, there is a feature for backup your local data to cloud storage https://docs.gitlab.com/ee/raketasks/backup_restore.html. This is useful in case your machine'HDD died suddenly)

To troubleshoot your problem smoothly, I'd advise not to modify your GitLab instance intentionally, for instance, applying own custom patch, changing database schema, etc.

Post reply on HN