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

GitLab Container Registry

about.gitlab.com

Post reply on HN
Print view View original

81–90 of 121 posts

Re: GitLab Container Registry

#81

Post by vonklaus »

sytse wrote: post #66
Cyph0n wrote: post #64

Earlier quoted context omitted.

Damn, you are one lucky person! Getting paid to work on OSS is a dream come true. Keep up the awesome work everyone :)

Thanks! And I think Connor created his own luck. People were assuming he already worked at GitLab since he was so active on social media and on our issue trackers. If you consistently contribute to GitLab it is very hard for us not to hire you.

I want to work on growth for Gitlab. Where are you guys seeing problems in market penetration so I can fill out an application[0].

[0] pun intented.

edit: To anyone interested, this is the public haml file that generates their website, to which they encourage contributions. So a pull request job application it is.

Re: GitLab Container Registry

#82

Post by stp-ip »

connorshea wrote: post #10

Kind of unrelated, but I'm super happy to be working at GitLab. Nearly everything we do is out in the open, and most features are available in CE, which is fully open source ( https://gitlab.com/gitlab-org/gitlab-ce ). I've wanted great, open source tools that don't look like dung for a long long time, and GitLab is definitely reaching that goal. Can't help but gush about the product we're building. :D Here are some…

Not to mention the awesome team at GitLab and the Core Team from the community. Awesome progress and quite transparent and with an amazingly open approach. Buffer with a product one wants to work on.

Re: GitLab Container Registry

#83

Post by drewcrawford »

sytse wrote: post #19
diggan wrote: post #14

I'm excited for this, seems like GitLab is moving more into a all-in-one solution, compared to Github that focuses on "social coding", whatever that now means. So to try out this new feature (together with the pipelines), I tried setting up a simple project that uses a docker image to serve a simple html page. However, it seems like it's not possible to build/push from the CI system (unless you setup a self-hosted ru…

Thanks, our idea is indeed to build an all-in-one solution. For more information see https://about.gitlab.com/direction/#scope You should be able to build/push from the CI system, see the example GitLab CI configuration file in the blog post. EDIT: For GitLab.com users using shared runners this is waiting on the Runner upgrade that we'll do in the coming days. If you use your own runner that runs 1.2 it should be fin…

Does this work for autoscale runners? Are those privileged by default?

Re: GitLab Container Registry

#85

Post by lfam »

justinsaccount wrote: post #65
davexunit wrote: post #33

Earlier quoted context omitted.

The problem is that Docker, and more generally using stacks of binary disk images, is fundamentally flawed with respect to security and reproducibility. It's nontrivial to inspect these images for vulnerabilities because there is nothing that specifies the precise set of software that is in that image. Some stuff is compiled from source, some stuff is installed via one or more package managers, each of which may bund…

Can I play too? The problem is that unix, and more generally any operating system, is fundamentally flawed with respect to security and reproducibility. It's nontrivial to inspect these installations for vulnerabilities because there is nothing that specifies the precise set of software that is in that installation. Some stuff is compiled from source, some stuff is installed via one or more package managers, each of…

Indeed. I recommend you look into one of the projects that is trying to mitigate this problem by allowing you to precisely specify, inspect, and change the dependency graph of software on your computer. That is, Guix or Nix.

Guix (and I presume Nix) can then take advantage of that transparency and control to build containers, virtual machines, and bare-metal systems to your specifications.

Re: GitLab Container Registry

#86

Post by tostaki »

allan_s wrote: post #32

In the same idea, has someone already worked integration with a debian repository (with aptly or similar) and has some linked to share on how to do it the smartway? We're thinking about using FPM to create the debian package Package which is the retrieve as the artifacts of the gitlab-ci build stage And then to have a separate service that will receive a webhook at the end of the (successful) build, to retrieve the a…

At my work, we have a setup close to this. On a successful build of jenkins (after build action), a deb is generated with FPM (awesome piece of software btw) and uploaded to an s3 bucket. Then on another machine, a cron that run every minutes sync the s3 bucket to a local aptly repository and publish it to another s3 bucket which is the real debian repository.

This works well but the s3+cron part is probably not the smartest way and publication can take some time (like 5-10min).

Re: GitLab Container Registry

#87

Post by [deleted] »

vonklaus wrote: post #81
sytse wrote: post #66

Earlier quoted context omitted.

Thanks! And I think Connor created his own luck. People were assuming he already worked at GitLab since he was so active on social media and on our issue trackers. If you consistently contribute to GitLab it is very hard for us not to hire you.

I want to work on growth for Gitlab. Where are you guys seeing problems in market penetration so I can fill out an application[0]. [0] pun intented. edit: To anyone interested, this is the public haml file that generates their website, to which they encourage contributions. So a pull request job application it is.

[deleted]

Re: GitLab Container Registry

#88

Post by edwinksl »

andromeduck wrote: post #43
r3bl wrote: post #41

Earlier quoted context omitted.

I really don't know what to hope for. All that I do now that I really enjoy watching what looks like a full on feature battle between GitLab and GitHub going on at this moment. As a guy who uses both (GitLab for my job, GitHub personally), I feel like I'm getting the best of both worlds. Although , to be perfectly honest, it feels to me like, at this point of the "feature battle", GitLab started embracing and actuall…

now if only they could get gitlab.com page loads consistently under 1 second... x_x

Yeah the site is taking a ridiculous amount of time to load.

Re: GitLab Container Registry

#89

Post by sytse »

Cyph0n wrote: post #80
sytse wrote: post #66

Earlier quoted context omitted.

Thanks! And I think Connor created his own luck. People were assuming he already worked at GitLab since he was so active on social media and on our issue trackers. If you consistently contribute to GitLab it is very hard for us not to hire you.

That's a pretty effective hiring method in my opinion. You guys should publish a blog post or something on your hiring practices and results - I'm sure the HN crowd would enjoy it.

Thanks, our hiring practices are detailed on https://about.gitlab.com/handbook/hiring/ what kinds of results should we include?

I'm also thinking about writing about an open organization, where the handbooks and issue trackers are public. Would that be interesting?

Re: GitLab Container Registry

#90

Post by sytse »

ymse wrote: post #75
nikolay wrote: post #73

Earlier quoted context omitted.

Yup! It supposedly is written in a much more efficient language, but it severely slower than GitHub and Bitbucket.

It's written in Ruby like Github, but the latter have considerably more experience running high-traffic systems. Just perused their job page and will apply this week. Sound like they could use some Varnish and Ceph talent :)

For sure we're interested in people that have experience with Ceph.
Post reply on HN