31–40 of 121 posts
If you haven't checked out gitlab in a while, you definitely should. It's been moving fast and come a long way lately.
Thank you Gitlab team for making an open source, self hosted platform and all the recent improvements you've made.
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 artifacts and update a repository using aptly.
Does it seems the right way or is there some much simpler solution ?
Awesome, a new place to host your unpatched, opaque disk images!
I think the patching of Docker container images is a big problem. We try to provide a completely automated flow in GitLab using CI, CD, and the container registry. I would love to have a big button that says 'update all my containers'. I've made an issue https://gitlab.com/gitlab-org/gitlab-ee/issues/592
In short, container images as popularized by Docker are insecure by design.
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? 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. Just won…
The biggest plus of using integrated registry is that you have integrated authentication and authorization of GitLab that follow your groups and members assigned to your GitLab projects, making it really easy to have private container repositories stored on registry. Second the built-in registry is really easy to configure and maintain. You have to specify the address and provide a certificate to start using it. You…
Earlier quoted context omitted.
I think the patching of Docker container images is a big problem. We try to provide a completely automated flow in GitLab using CI, CD, and the container registry. I would love to have a big button that says 'update all my containers'. I've made an issue https://gitlab.com/gitlab-org/gitlab-ee/issues/592
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…
Of course I'm looking at this from the perspective of deploying micro-services and immutable infrastructure. Your use-case may be different.
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…
They are on a roll, rolling out features left and right and seem to nail the need for every engineer.
Kudos to the team! Keep rocking!
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…
My configuration looks like this currently (and I'm guessing I'll hold of for a few days for the shared workers to get updated):
image: docker:latest
services:
- docker:dind
stages:
- build
- deploy
build:
stage: build
script:
- docker build -t registry.gitlab.com/victorbjelkholm/deploy-html-test:latest .
only:
- master
deploy:
stage: deploy
script:
- docker push registry.gitlab.com/victorbjelkholm/deploy-html-test:latest
only:
- masterIn 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…
Depending what it is you're building, using the proper debian tooling (dpkg-buildpackage, etc) is not that much harder than FPM, and cooperating with the system gives you a lot of goodies for free (sourcedebs, cowbuilder, etc).