tmaczukin

4 ms·

1.
by tmaczukin 8y ago
> - we do not use kubernetes so eveything CD is off the plate for us (environment and monitoring tab are useless) Environments can be useful even without integration with K8S. It's useful e.g. for review apps feature ( https:/&
2.
by tmaczukin 8y ago
You can use images hosted on GitLab's Container Registry. Especially - you can use such images as the base for CI/CD jobs running on the same GitLab instance. It was possible since very erly state of GitLab's Container Regist
3.
by tmaczukin 10y ago
maktouch: Runner can't connect to GitLab because version 9.0 of Runner requires GitLab 9.0. We've noticed this in the release blog post: https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#
4.
by tmaczukin 10y ago
For other who are seeing this issue: 'gitlab-ctl reconfigure && gitlab-ctl restart' should resolve this problem without a need to reboot the machine. The problem is tracked in https://gitlab.com/gitlab-org&
5.
by tmaczukin 10y ago
Hey jancsika, As Kamil already wrote, the number of notifications, issues and merge requests that we follow is enormous and sometimes something may be missed. I'm doing my best to have eye on everything but this is not always possible.
6.
by tmaczukin 10y ago
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.
7.
by tmaczukin 10y ago
Our shared runners should be updated within a week. Then you will be able to use Container Registry on GitLab.com without self-hosted runner.