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

91–100 of 121 posts

Re: GitLab Container Registry

#91

Post by sytse »

Tiksi wrote: post #79
sytse wrote: post #70

Earlier quoted context omitted.

Thanks for your kind words. May I ask what supporting infrastructure you'll set in 3 weeks from now? We'll have to add it to the schedule for 8.9

Well since you asked, I'm working on a system that writes perfect bug-free code for me, but if you can implement that I'll save myself the effort. But really, the next thing on the roadmap is to get tighter integration between our CFM (saltstack/salt-api) and gitlab. Tie it into deploys, auto-open issues on failed states, etc., though that's gonna be more on the salt side than the gitlab side and likely wouldn't make…

It would be nice to upload Salt modules directly from GitLab.

Since you can deploy from GitLab too, auto-opening issues for failed builds makes sense. I opened an issue on https://gitlab.com/gitlab-org/gitlab-ce/issues/17771

I predict you'll be setting up different environments a week before 8.9 since that is what we'll ship.

Re: GitLab Container Registry

#92

Post by sytse »

drewcrawford wrote: post #83
sytse wrote: post #19

Earlier quoted context omitted.

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?

It is about the Runners needing to be on version 1.2. We'll upgrade the .com autoscaling ones in the coming days. If you run your own autoscaling runners you can upgrade yourself.

Re: GitLab Container Registry

#93

Post by sytse »

netcraft wrote: post #74
tmaczukin wrote: post #25

Earlier quoted context omitted.

You can enable Container Registry for your projects on GitLab.com :) And in a few days our shared runners should be updated to support the full docker workflow with the Container Registry.

thats really amazing - are there size limits?

Our soft limit is 10GB per project for GitLab.com https://about.gitlab.com/gitlab-ci/

Re: GitLab Container Registry

#94

Post by ymse »

davexunit wrote: post #7

Awesome, a new place to host your unpatched, opaque disk images!

The registry is just that: a registry. You can push a Guix-generated image to it if you wish and use with any container runtime. rkt supports the same API; the Docker relation is by name only.

In fact, being able to push static images directly to such a registry with Guix would be a great feature. Both for continuous integration (without needing Hydra) and for coupling with a cluster scheduler such as Kubernetes.

Re: GitLab Container Registry

#95

Post by agibsonccc »

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.

Not to jump on to the gitlab bandwagon here. Adam from Skymind (YC W16) here

I just want to say the last 4 hires we've made (we're only 11 soon 12) have been from around the world (we're in 4 countries) and this has worked great for us. A thriving open source community is key to hiring for us. A lot of our team does some sort of traveling.

I myself will be working from tokyo (currently in korea actually..) moving from SF.

We make the time zones work :D. Key to that for us has been gitter where we can collaborate/support the open source community while also being able to use it for collaborating with partners and running things like training classes.

Just wanted to provide another example to prove gitlab isn't an anomaly. The same is true for a lot of the larger open source organizations (eg: canonical,redhat,automattic)

Re: GitLab Container Registry

#96

Post by alfg »

So awesome! I've been invested into the Docker ecosystem lately and one of the next things I've wanted to setup is a decent CI workflow.

I wish Github would also ship more features at the pace Gitlab is. The only issue I've had with Gitlab are the response times on their UI. Hopefully they sort that out soon.

Re: GitLab Container Registry

#97

Post by zanny »

r3bl wrote: post #41
nikolay wrote: post #4

At this pace of innovation, GitHub will soon be a part of the history! GitHub has done a tremendous job with forking and pull requests, but, at least recently, they've acted disorientedly! I hope they get back into shape!

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…

Considering Gitlab is the more open source of the two, the answer has to always be gitlab.

Albeit, it still sucks most free software communities cannot use self-hosted gitlab because too many features are stuck in the enterprise edition, but its way better than what github is offering, which is nothing.

Re: GitLab Container Registry

#99

Post by kaishiro »

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…

Sorry if this is the wrong venue to ask this, but any idea if/when Codeship will natively support you guys?

It's honestly my one hangup since we do all of our deploys there.

Re: GitLab Container Registry

#100

Post by dblessing »

stp-ip wrote: post #82
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.

Thanks for recognizing our Core Team, too. They're an integral part of our community. :)
Post reply on HN