Kind of unrelated, but I'm super happy to be working at GitLab.<p>Nearly everything we do is out in the open, and most features are available in CE, which is fully open source (<a href="https://gitlab.com/gitlab-org/gitlab-ce" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce</a>). 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<p>Here are some of my favorite upcoming features: <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/17575" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/17575</a>, <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/14661" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/14661</a>, <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/15337" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/15337</a>
Fantastic, Gitlab are absolutely nailing it at the moment. Don't think there's any other hosted service offering so many CI/CD features for free under one roof.<p>It feels like what Github did for SCM, Gitlab are doing for CI.
These days it seems that Docker is everywhere. I am new to docker and I seem to find it as one more additional complicated system that the developer now needs to learn in order to deploy his or her application.<p>How useful do you find docker for application which can be deployed on Heroku or Beanstalk? I can understand using docker for a Language ecosystem which is not supported on Public PaaS. Or for people for whom public PaaS is not an option.<p>I would like to know about the experience of using Docker in day to day development from people who have used Docker in team environments. How was your experience of converting the team to use Docker instead of their regular development/deployment? For example, at our company, For LAMP or MEAN or Java Stacks, we have a defined a procedure of setting up the dev machines to include all these tools and developers know how to manage these on their own machine. Once the code is pushed to Jenkins, there are deploy scripts written by tech leads which take care of deployment to various servers or to Heroku.<p>In your Docker driven development process, did everybody started using docker on their development machine too? Or everybody just kept using their local setup, and only one/two people handled the task of creating final docker images? Or do you just use you CI server to handle the docker image creation and deployment from that point onwards?
It seems like every time I set up some supporting infrastructure it ends up rolled into the next gitlab release a week later, not that I'm complaining (much).<p>If you haven't checked out gitlab in a while, you definitely should. It's been moving fast and come a long way lately.<p>Thank you Gitlab team for making an open source, self hosted platform and all the recent improvements you've made.
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!
Everyone at GitLab has been doing an amazing job shipping some really cool features.<p>I'm really looking forward to trying out the new container registry and move away from my hack-y solution that I use right now to build Docker images on my own VM, and move back to the shared runners :)
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.<p>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.<p>However, it seems like it's not possible to build/push from the CI system (unless you setup a self-hosted runner) which kind of leaves this "Container Registry" without value, because I still need to manually build/push my images from one machine...
After GitHub moved to unlimited repositories, I started to question if our small team should stay on GitLab - and this just triple-confirmed that we will.<p>Awesome feature for an already awesome product. Great job!
Up until recently I never even considered using CI in my projects because I just didn't have the time. The way GitLab are implementing all these tools makes it not only easy to use, but fun.
Interesting move.<p>Seems Gitlab are moving fairly fast (compared to competition) and going for that all in one ecosystem (If you want it) from SCM to deployment with the range of products they've introduced.
Other good news for GitLab: Zach Holman just joined them as an advisor!<p><a href="https://mobile.twitter.com/holman/status/734842346278244352" rel="nofollow">https://mobile.twitter.com/holman/status/734842346278244352</a>
Gitlab is what Github was 3 years ago.<p>They are on a roll, rolling out features left and right and seem to nail the need for every engineer.<p>Kudos to the team! Keep rocking!
Can I use gitlab container registry with gitlab.com? Can I use private images in said registry with public gitlab.com ci builders?
I haven't found a way to use private containers with gitlab.com ci yet without spinning up a worker for every project.
Maybe a way to register a "team wide" builder?
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.<p>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.
I wish Gitlab had an easy clean way to import GitHub. The current method involves setting up oauth information in the config file and restarting gitlab. Not nice :/ I fail to see why they cannot just work with GitHub API tokens for import?
This is great! But I'm curious if anyone at Gitlab can comment on what this gives over running the existing docker registry? Can we configure this to use S3 to store the resulting images?<p>Our runner image has docker, we run our tests with docker-compose, if they pass we push them to our existing registry. In fact our .gitlab-ci.yml looks very similar to the example under "elaborate example" in the blog post.<p>Just wondering what we'd be missing out on if we didn't switch to Gitlab Container Registry.
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?<p>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<p>And then to have a separate service that will receive a webhook at the end of the (successful) build, to retrieve the artifacts and update a repository using aptly.<p>Does it seems the right way or is there some much simpler solution ?
I've tried several times to figure out how to get Docker working in a situation like mine. And we've been considering GitLab as well. So this is likely a good time to experiment.<p>Doing all the research on how to integrate Docker into my particular situation has been daunting. I really need to track down some online courses or something. The articles just aren't cutting it. Or need to find a mentor just to ask stupid questions to.
Looks great. One thing that does not appear to be clear though is if you build multiple docker images from the same project.<p>Our deployment workflow at the moment builds two docker images, one for the web app and another for the background services. Both share the same code.<p>It would appear you can only have one docker image per project?
am I correct that this is only for on-prem deployments, that they aren't going to be offering a public container registry a la docker hub or quay?