2 ms·
I use self-hosted gitlab as my primary CI and love it. Setting up CI runners is still too complicated (maybe because I use the gitlab docker image and there's n
by awinter-py 11y ago
I use self-hosted gitlab as my primary CI and love it. Setting up CI runners is still too complicated (maybe because I use the gitlab docker image and there's no compose support). drone.io seems to have better support for deploying & cleaning up images, but I'm sure gitlab will get there.
- jobvandervoort 11y agoGreat to hear. We're working on making deploy [0] and working with Docker images [1] easier. That should also include cleanup in time. I owe you a reply regarding Docker Compose support. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/3286 https://gitlab.com/gitlab-org/gitlab-ce/issues/3286 [1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/634274 https://gitlab.com/gitlab-org/gitlab-ce/issues/634274
- awinter-py 11y agoThanks -- didn't realize they added an artifacts key to the CI yaml.
- sytse 11y agoYou're welcome. To read more about build artifacts please see http://doc.gitlab.com/ce/ci/build_artifacts/README.html http://doc.gitlab.com/ce/ci/build_artifacts/README.html
- awinter-py 11y agoI'm sure you hear this a lot, but thanks & keep up the good work. I'm grateful for all the great open source tools I use, but you guys are in the upper echelon for making consistent forward strides without breaking too much.
- sytse 11y agoThanks! Comments like yours are an inspiration to us, I'll share with the team (now 70+ people!).
- eterps 11y agoI'm also interested in compose support.