Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ayufan
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
ayufan
9y ago
Ok. So most of these problems are related to Runner and Docker Containers for builds: 1. You can make Runner to not create cache containers with Advanced Settings and `disable_cache` option, 2. As for Git Repo, you can force Runner to retry
2.
▲
by
ayufan
9y ago
Could you point to problems and ideally issues that you are facing? Kamil, GitLab CI/CD Lead
3.
▲
by
ayufan
9y ago
Thanks. We are aware of this issue, and we even know what is causing that, we also have ideas how to fix that. The plan is to release a fix with 10.5: https://gitlab.com/gitlab-org/gitlab-ce/issues/38265#note_
4.
▲
by
ayufan
10y ago
Hi janciska, Thanks for writing that comment and making us aware of that case. I'm very sorry that it did that long to get reviewed and merged. The number of issues and merge requests that pass our hands is just crazy and sometimes it
5.
▲
by
ayufan
10y ago
Hi maktouch, 1. Since the review apps is tied with a branch, as soon as branch is deleted the review app is stopped. This actually happening in above video. At the end you see the stopped review :) 2. You can use your own services. Sid did
6.
▲
by
ayufan
10y ago
Currently not. The limitations can be found here: http://docs.gitlab.com/ce/container_registry/README.html#lim... . We plan to improve that in one of upcoming releases.
7.
▲
by
ayufan
10y ago
The Container Registry is available on our free GitLab.com.
8.
▲
by
ayufan
10y ago
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 repos
9.
▲
by
ayufan
10y ago
We are thinking big. The integrated Container Registry is part of our plan. We will soon have an integrated deployments with easy to access environments. We also plan to introduce manual actions on pipelines allowing you to execute arbitary
10.
▲
by
ayufan
10y ago
Thanks. We are working on bringing missing features to artifacts, so we will improve that workflow.
11.
▲
by
ayufan
10y ago
We are already considering that and given past experience it is a quite simple process: https://gitlab.com/gitlab-org/gitlab-ce/issues/14926 GitLab CI Lead
12.
▲
by
ayufan
11y ago
Thanks tobilg. We choose docker-machine, because it also manages infrastructure, so this makes it much more easier for Administrators to manage hundred of build machines. I'm thinking about an option to make it possible in one of the u
13.
▲
by
ayufan
11y ago
This was problem in the past. Since we use Docker we have fairly good separation of builds. You are not able to fetch someone other source unless you find or use linux kernel exploit. This will get improved further with upcoming upgrades to
14.
▲
by
ayufan
11y ago
Currently Shared Runners offer only Linux-based builds. We can introduce extensions to that offering at some point. The Linux-based Shared Runners are free for everyone, including for private projects.
15.
▲
by
ayufan
11y ago
Exactly. The image specified during registration is the default one. You can override the image globally in .gitlab-ci.yml or on per-job basis. Full flexibility here :)
16.
▲
by
ayufan
11y ago
I understand your reasoning. At this point it doesn't make sense to introduce support for another clustering manager. The GitLab Runner does support docker-machine (you can pretty easily configure it to create machines on-demand on any
17.
▲
by
ayufan
11y ago
You shouldn't be. Executing builds on Kubernetes is not the same as deploying an application :) We will solve that need with plugins :) GitLab CI Lead
18.
▲
by
ayufan
11y ago
You may be interested in this example of Python application (django): http://doc.gitlab.com/ce/ci/examples/test-and-deploy-python-...
19.
▲
by
ayufan
11y ago
Previously we had problems with usernames/groups that had upper case letters. The recent improvements (8.5) fixes all these problems. Please try it now :)
20.
▲
by
ayufan
11y ago
Yes. Sure. Instead of adding the CNAME you need to add an A record. You can get the IP address with dig: $ dig a myuser.gitlab.io Then configure your domain to point to that IP address. We are currently working on documentation covering tha