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

71–80 of 117 posts

Re: GitLab 8.15 Released

#71

Post by Heliosmaster »

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…

To be honest, the APT package is easy to configure, runs flawlessly and updates seamlessly.

Re: GitLab 8.15 Released

#72

Post by grzesiekb »

wernerb wrote: post #24

As a paying gitlab ee customer, we love to use gitlab. I just have one gripe with review apps. We would really like you to open it up with an API. Allowing us to create the infrastructure outside of gitlab-ci and setting the reviewapp url/domain etc using the API would be extremely valueable for us, as we are stepping off of the gitlab-ci, but would very much like the UI interface upgrades review apps provides. We ar…

Thanks for this feedback! At GitLab, we believe that work is never done, and we are always looking for things we can improve, in our CI solution as well! Let me address some of your concerns:

1. There is only one pipeline allowed at the moment (see issue about support for multiple pipelines: https://gitlab.com/gitlab-org/gitlab-ce/issues/22972), but you can use multiple builds / stages to usually achieve the same. We also plan to add ability to control status using exist code from the build (see https://gitlab.com/gitlab-org/gitlab-ce/issues/25738). You can also use our pipeline trigger API with environment variables to control what get executed.

2. That is true, we already did some backstage work to improve that. In the meantime it is possible to explicitly depend on builds from the previous stages to download all artifacts in subsequent jobs.

3. I'm not sure if I understand correctly, what you want to accomplish, but if `[ci skip]` is not enough, then status based on the exit code may be helpful as well.

Re: GitLab 8.15 Released

#73

Post by sytse »

icebraining wrote: post #61

Oh man, oh man, global hooks! Thank you! The other features are awesome, but this is the one that will get us to upgrade right now! We use dozens of repositories, and it's been a pain to manually configure and update hooks.

Glad to hear that, and thanks for posting. Happy holidays!

Re: GitLab 8.15 Released

#74

Post by pawadu »

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.

Well, F-droid is a pretty huge organization in terms of user count and repo activity: https://gitlab.com/fdroid

Otherwise, you can see the most star-ed repos here: https://gitlab.com/explore/projects/starred

(I think more people should consider moving from github to gitlab or bitbucket, but for gods sake avoids googles new git site).

Re: GitLab 8.15 Released

#75

Post by sytse »

robinhood wrote: post #12
ylere wrote: post #11

Wow, that is an amazing release. Seems you actually managed to complete your goal right before christmas! This whole year has been quite impressive, I can't wait to see what you will do in 2017.

Thanks! We are super happy to have completed our vision on Idea to production this year. We'll keep improving and innovating in 2017, you can count on that :-)

One of the things we'll do is to make sure everyone can replicate the idea to production flow, see https://gitlab.com/gitlab-org/gitlab-ce/issues/25986

I'm also excited about adding Prometheus monitoring for apps you deploy https://www.youtube.com/watch?v=NFPGtbQfL1A

Re: GitLab 8.15 Released

#76

Post by sytse »

softinio wrote: post #40
chncdcksn wrote: post #36

Earlier quoted context omitted.

That's really strange; I received an email today, with the previous emails being on the 8th and on Nov. 22. What is the contents of the emails, and what address are they from? Are they duplicate emails? Sounds like someone impersonating GitLab.

taking a quick look: community@gitlab.com news@gitlab.com kris@gitlab.com All marketing their features and help to get started. Like I said nothing wrong with sending this kind of email just over a certain period in moderation. Everything in life is relative isn't it :-)

Thanks for the addresses the emails came from. I've shared it with our marketing team.

Re: GitLab 8.15 Released

#77

Post by nmrony »

chmln wrote: post #16
no_protocol wrote: post #7

Earlier quoted context omitted.

Can you share what these items are? I have used GitLab quite a bit and GitHub just a little, and I so far have enjoyed using GitLab much more. I had a hard time finding my way around on GitHub. The main parts I've used in both are creating Issues and Merge Requests, and in GitLab I've accepted them and managed teams/projects.

Sure, some things off the top of my head: - On the main project page, the file list/table cells have too much padding. The same project's file list, with 22 files, on GitHub fits on my screen comfortably. On Gitlab, the whole table sits at 928px in height. Reducing the top/bottom padding in cells to 5px, without a loss in usability, yields a much nicer 708px height - The two panels above the file list (the branch, an…

Hi chmin, thanks a lot for your suggestion. We will look into it. Please feel free to open an issue regarding that if you want. We are also considering about the line length in a file so that people find it more friendly to read. https://gitlab.com/gitlab-org/gitlab-ce/issues/13680. Thanks again for your suggestion :-)

Re: GitLab 8.15 Released

#78

Post by contingencies »

sytse wrote: post #62
contingencies wrote: post #53

Earlier quoted context omitted.

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

The image Cidan referred to was last pushed 5 hours ago when we released 8.15 and should always be up to date. For more information about our official docker images see https://docs.gitlab.com/omnibus/docker/README.html I've added a section to say that these images are officially supported with https://gitlab.com/gitlab-org/omnibus-gitlab/commit/26501d91... If you experience problems with them please feel free to fil…

should always be up to date

OK. I definitely remember running in to something that looked official but wasn't up to date (remotely) a few weeks ago. Perhaps it was this image, perhaps not. IIRC at the time I was judging only from the 'updated [time periods] ago' data in the docker hub webpages.

Re: GitLab 8.15 Released

#79

Post by Rapzid »

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.

I look forward to seeing the open source libgit2 storage backends :)

Re: GitLab 8.15 Released

#80

Post by pslijkhuis »

snuxoll wrote: post #37
hackerboos wrote: post #29

I love how easy the integration with Openshift is. Does anyone have any resources to get a Openshift Kubernetes cluster setup?

Actually, it's incredibly easy, especially in tandem with CentOS Atomic Host. Here's my setup at work I just deployed last month: osm01-03 - OpenShift masters, don't run anything other than OpenShift services (Atomic host) osn01-03 - OpenShift nodes, actually run the apps (Atomic host) osnlb - Load balancer for the master (CentOS 7) oss - NFS server providing storage for OpenShift docker images (CentOS 7) On your sto…

Thanks for the write up. It sounds like a great setup.
Post reply on HN