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

GitLab 8.15 Released

about.gitlab.com

Post reply on HN
Print view View original

51–60 of 117 posts

Re: GitLab 8.15 Released

#51

Post by Cidan »

contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

Pardon me here, but I don't understand what you mean by "the docker image most people use is unofficial."

I was under the impression that everyone used the fully featured official docker image (https://hub.docker.com/r/gitlab/gitlab-ee/). We've been using this for over a year without issues now. Is there a reason you need the unofficial version? Does it do something different?

Re: GitLab 8.15 Released

#52

Post by CSDude »

contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

We have been using the official Docker image without any problems so far.

Re: GitLab 8.15 Released

#53

Post by contingencies »

Cidan wrote: post #51
contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

Pardon me here, but I don't understand what you mean by "the docker image most people use is unofficial." I was under the impression that everyone used the fully featured official docker image ( https://hub.docker.com/r/gitlab/gitlab-ee/ ). We've been using this for over a year without issues now. Is there a reason you need the unofficial version? Does it do something different?

IIRC because last time I checked it had no comments/community around it and was until recently out of date.

Re: GitLab 8.15 Released

#54

Post by napsterbr »

lbotos wrote: post #48
napsterbr wrote: post #34

Earlier quoted context omitted.

Don't know exactly why you decided against moving to bare metal, but IMO you definitely should. We've got tremendous improvements moving to metal. I also can't recommend OVH enough. Best price on market plus great hardware and uptime. Technical support isn't the best but you shouldn't need it anyway.

I also work at GitLab on a non-infra team. Here is Sid's explanation: https://gitlab.com/gitlab-com/infrastructure/issues/727#note... I, personally, was apprehensive of going to bare metal for most of the reasons that Sid lists in the above message, and I think that making the app just _better_ is where we should focus before we try and run to pure hardware to solve the problem.

Thanks for the link. I understand the rationale, it's definitely not a simple decision, but if these improvements can be made at the application layer then by all means go for it.

Re: GitLab 8.15 Released

#55

Post by AaronFriel »

contingencies wrote: post #25
connorshea wrote: post #18

Earlier quoted context omitted.

Thanks for the honest feedback, it's genuinely useful for improving the product. Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.

Even if I trusted it not to munge other things (doubtful), IIRC omnibus does not support my distro (Gentoo), and setting up another distro I have to (remember to) maintain just to support one application does not appeal medium term versus using a popular docker image which has done that for me already in a pre-tested fashion and should handle maintenance smoother. Basically I'm at this point: 'what's the easiest self…

I don't think your concerns are founded, I just deployed GitLab for personal use on a virtual machine with the omnibus image (gitlab-ce:latest) and it worked flawlessly. And since they released an update today, to upgrade all I had to do was:

    docker pull gitlab/gitlab-ce:latest
    docker stop gitlab
    docker rename gitlab gitlab-old
    docker run --detach --publish 60100:80 --publish 58432:22 --name gitlab --restart always \
         --volume /var/volumes/gitlab/config:/etc/gitlab \
         --volume /var/volumes/gitlab/logs:/var/log/gitlab \
         --volume /var/volumes/gitlab/data:/var/opt/gitlab \
         gitlab/gitlab-ce:latest
    
    # after verifying the new image works, docker rm docker-old; docker rmi [old image].
It took less than an hour to configure it for external SMTP relay, external auth with two factor authentication, etc.

I did just get started with it, but I have to say the omnibus install was fairly easy.

Re: GitLab 8.15 Released

#56

Post by contingencies »

AaronFriel wrote: post #55
contingencies wrote: post #25

Earlier quoted context omitted.

Even if I trusted it not to munge other things (doubtful), IIRC omnibus does not support my distro (Gentoo), and setting up another distro I have to (remember to) maintain just to support one application does not appeal medium term versus using a popular docker image which has done that for me already in a pre-tested fashion and should handle maintenance smoother. Basically I'm at this point: 'what's the easiest self…

I don't think your concerns are founded, I just deployed GitLab for personal use on a virtual machine with the omnibus image (gitlab-ce:latest) and it worked flawlessly. And since they released an update today, to upgrade all I had to do was: docker pull gitlab/gitlab-ce:latest docker stop gitlab docker rename gitlab gitlab-old docker run --detach --publish 60100:80 --publish 58432:22 --name gitlab --restart always \…

Great, I'm glad it worked for you. It didn't work for me and other people, as per the issues linked. When it doesn't work, there's no clearly defined debug path, and very little response.

Re: GitLab 8.15 Released

#57

Post by desireco42 »

contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

I thought the same thing :) How did things get so complex :)

Re: GitLab 8.15 Released

#58

Post by grumblestumble »

angry-hacker wrote: post #39

Are there notable projects or organizations moved to gitlab.com? On top of my head I only know f-droid that is there. I use it for personal use and love it, would love if more projects moved away from github.com, especially open source.

i think the killer feature of gitlab is still self-hosted instances. it makes it really hard to justify using github enterprise. as far as gitlab.com, i've toyed around with it on personal projects and it still has a very long way to go in terms of reliability and speed.

Re: GitLab 8.15 Released

#59

Post by gtaylor »

theptip wrote: post #50
gtaylor wrote: post #41

Earlier quoted context omitted.

There is indeed a helm package, gitlab-ce.

Aha! I was looking for this recently. Doesn't appear to be on https://about.gitlab.com/installation/ , which is where I stopped my search for it.

It's very new and still maturing. Pull requests and improvements welcome!

Re: GitLab 8.15 Released

#60

Post by AaronFriel »

contingencies wrote: post #56
AaronFriel wrote: post #55

Earlier quoted context omitted.

I don't think your concerns are founded, I just deployed GitLab for personal use on a virtual machine with the omnibus image (gitlab-ce:latest) and it worked flawlessly. And since they released an update today, to upgrade all I had to do was: docker pull gitlab/gitlab-ce:latest docker stop gitlab docker rename gitlab gitlab-old docker run --detach --publish 60100:80 --publish 58432:22 --name gitlab --restart always \…

Great, I'm glad it worked for you. It didn't work for me and other people, as per the issues linked. When it doesn't work, there's no clearly defined debug path, and very little response.

Respectfully, it seems like you are using the wrong Docker image, and that's the source of your troubles. Others have commented similarly, and I think that you are too easily dismissing them.
Post reply on HN