Live data from Hacker News

Gitlab 10.7 Released

about.gitlab.com

41–50 of 84 posts

Re: Gitlab 10.7 Released

#41
post #27
post #23

Earlier quoted context omitted.

Awesome that your upgrades are smooth, thanks for posting. We're indeed a completely remote team, see https://about.gitlab.com/culture/remote-only/ And we do want to make sure that all the features you really need are there. I understand the VideoLan needs https://gitlab.com/gitlab-org/gitlab-ce/issues/40321 and we're prioritizing it.

> We're indeed a completely remote team, see https://about.gitlab.com/culture/remote-only/ That's very hard to keep at a constant pace. > And we do want to make sure that all the features you really need are there. So far, everything is great, but we would love to have: - Custom Fields, in order to leave trac (such a pain, this service is); - A way to fork/MR across Gitlab/Github instances: we don't want our instance…

> A way to fork/MR across Gitlab/Github instances

I think ActivityPub would be a good fit for federation across GitLab instances and would have a real chance to displace Github for open-source projects, if implemented right.

Re: Gitlab 10.7 Released

#42

I implemented the HTTPS-only Pages feature in this release. I just wanted to say that GitLab is a great project to contribute to, with a very friendly and professional community! Definitely recommend to anybody interested in contributing to a project themselves. [1] https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16273 [2] https://about.gitlab.com/contributing/

Please add the mirror functionality to CE.

Re: Gitlab 10.7 Released

#43
Is there any roadmap for how the cloud-native chart is progressing? I’m really interested in switching to that, as the current implementation takes almost 15 minutes to restart and uses over 8GB RAM when idle for me.

Re: Gitlab 10.7 Released

#44
There seem to be several people involved with GitLab here, so maybe one of you would be kind enough to answer the question I've had for a long time: what exactly is GitLab? I've met several people who speak well of it or mention particular things they use it for, so I have to assume there is something very useful in there, but unfortunately I've always found the web site more confusing than enlightening.

Re: Gitlab 10.7 Released

#45
post #38

Earlier quoted context omitted.

Thank you. The issue thread/request for this had been open for something like 2 years and I waited patiently for someone braver than me to implement it. Now my custom domain on GitLab Pages automatically redirects to HTTPS. I'm happy. Next up is to add an option to automatically renew Let's Encrypt certs for GitLab Pages.

Automatic renewal has also been added in 10.7: https://docs.gitlab.com/omnibus/settings/ssl.html#automatic-...

Quick note, the existing Let's Encrypt integration does not support Pages. We are working on it, but it's worth noting Pages has multiple modes it can run in.

One is by setting up wildcard domains at the server level, like we have on GitLab.com with gitlab.io. We have an issue open for this, but the primary challenge is that Let's Encrypt requires DNS-01 validation for wildcard certificates, with a new challenge each renewal. That is difficult to automate through our Omnibus package. The issue tracking this work is here: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/3342

The other method allows users bring their own "custom domains": https://docs.gitlab.com/ee/administration/pages/#custom-doma...

This is easier to manage, as we can do HTTP or SNI validation for each domain without hitting LE's rate limits. We are working on this now here: https://gitlab.com/gitlab-org/gitlab-ce/issues/28996

Re: Gitlab 10.7 Released

#46

Earlier quoted context omitted.

@jancsika you could implement a whitelist using this feature, by having jobs only run for specific usernames. Keep in mind though that these variables can be overridden, so it probably shouldn't be used for security reasons: https://docs.gitlab.com/ce/ci/variables/README.html#priority... To give a more detailed example on the nightly build, you would create a pipeline schedule that ran once per day and specified a va…

Let me see if I understand it. Let's say I whitelist user "me" and user "foo" using this variable in the .gitlab-ci.yml. Let's also assume I have runners locked to my repo. Doing nothing else than that, user foo now submits a merge request from their fork to my repo. Does CI now run for that merge request?

If it is a forked project, CI should run in their own project I believe. It should not run on your Runners.

Re: Gitlab 10.7 Released

#47
post #27
post #23

Earlier quoted context omitted.

Awesome that your upgrades are smooth, thanks for posting. We're indeed a completely remote team, see https://about.gitlab.com/culture/remote-only/ And we do want to make sure that all the features you really need are there. I understand the VideoLan needs https://gitlab.com/gitlab-org/gitlab-ce/issues/40321 and we're prioritizing it.

> We're indeed a completely remote team, see https://about.gitlab.com/culture/remote-only/ That's very hard to keep at a constant pace. > And we do want to make sure that all the features you really need are there. So far, everything is great, but we would love to have: - Custom Fields, in order to leave trac (such a pain, this service is); - A way to fork/MR across Gitlab/Github instances: we don't want our instance…

Thanks for sharing more info about this jbk.

> - A way to fork/MR across Gitlab/Github instances: we don't want our instance to become yet another forge, people should use gitlab.com/GH. We would like that people can fork our projects on gitlab.com/github.com and then send PR our way. I understand this is über-hard, but that would be very nice;

We actually have an issue open about it - https://gitlab.com/gitlab-org/gitlab-ce/issues/4013. As the issue label suggests, it's definitely a moonshot, but completely achievable in small steps / iterations.

> - Custom Fields, in order to leave trac (such a pain, this service is);

This one's on our radar as well - https://gitlab.com/gitlab-org/gitlab-ee/issues/1906

> - Be able to update a MR without push-forcing on the same branch, but with a new branch (that allows better reviewing of older versions).

Could you rephrase this? I think I'm missing the point. You can update a MR with a regular push. You can also browse through different versions of a MR diff (https://docs.gitlab.com/ee/user/project/merge_requests/versi...). A force push "is required" only if your local history doesn't match the remote history.

Re: Gitlab 10.7 Released

#48

There seem to be several people involved with GitLab here, so maybe one of you would be kind enough to answer the question I've had for a long time: what exactly is GitLab? I've met several people who speak well of it or mention particular things they use it for, so I have to assume there is something very useful in there, but unfortunately I've always found the web site more confusing than enlightening.

Glad to hear you're interested Silhouette!

> what exactly is GitLab?

Here's a couple of points that might shed some more light on it: https://about.gitlab.com/about/.

IMHO the first point nails it pretty well: "GitLab is a single application with features for the whole software development and operations (DevOps) lifecycle."

> I've always found the web site more confusing than enlightening.

Did you take a look at our homepage (https://about.gitlab.com) recently? (we updated it not too long ago)

Which part of it do you find confusing? We'd love to make it better. If more direct feedback is your thing, you can also open an issue about it in https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issu...

Re: Gitlab 10.7 Released

#49
post #43

Is there any roadmap for how the cloud-native chart is progressing? I’m really interested in switching to that, as the current implementation takes almost 15 minutes to restart and uses over 8GB RAM when idle for me.

The project hosting our WIP cloud-native chart is public and available at https://gitlab.com/charts/helm.gitlab.io

It's currently in Alpha. You can see a list of ongoing efforts in https://gitlab.com/charts/helm.gitlab.io/issues

Re: Gitlab 10.7 Released

#50

Earlier quoted context omitted.

> The whole reason for tech to exist is to improve things around the world Thats a pretty bold claim. Do you think this is true of all "tech" or just software? Do you think it similarly wasteful when a car manufacturer spends resources building yet-another-car? > ... yet brilliant minds are still spending years building one IDE after another. Who do you think _should_ get to decide what brilliant minds should spend t…

Um. A car is not software. How do I do a pull request for a new clutch. I hear ya. But your analogy is buggy.

They said tech. My question was if they would apply the same logic to physical engineers, they they should be spending their time differently.
Post reply on HN