61–70 of 121 posts
I'm really impressed by the hard work of GitLab team, keep it up! If anybody from GitLab is reading: any plans for rkt support?
Thanks! No current plans for rkt, but feel free to create an issue to discuss it.
Looks great. One thing that does not appear to be clear though is if you build multiple docker images from the same project. 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. It would appear you can only have one docker image per project?
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. It feels like what Github did for SCM, Gitlab are doing for CI.
Thanks Luke! We'll try to keep this going. We're working on deployment environments for our next release so you can see what is deployed in each environment. After that we can do deployments that need to be confirm manually.
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…
Keep up the awesome work everyone :)
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…
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 which may bundle additional software that one may not know about if they didn't inspect each piece of software carefully. Furthermore, one cannot even verify the installation reasonably because the results are different depending on when it was installed.
In short, operating systems are insecure by design.
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…
Damn, you are one lucky person! Getting paid to work on OSS is a dream come true. Keep up the awesome work everyone :)
Earlier quoted context omitted.
Thanks Luke! We'll try to keep this going. We're working on deployment environments for our next release so you can see what is deployed in each environment. After that we can do deployments that need to be confirm manually.
Wow, that's great news. Exactly what we are looking for. I was investigating to use GitLab CI to build, and then only deploy commits with a certain tag, but a dedicated workflow for deployments is much more convenient and less error-prone.
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
There are interesting challenges that currently make this none trivial but expect things to improve greatly in the near future.
Looks great. One thing that does not appear to be clear though is if you build multiple docker images from the same project. 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. It would appear you can only have one docker image per project?
AFAIK you can just have 2 stages to build each image and push both under different tags.
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). 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.