dgruesso

4 ms·

1.
by dgruesso 7y ago
GitLab PM here. As part of 11.10, we introduced the ability to disable Auto DevOps at the group-level ( https://docs.gitlab.com/ee/topics/autodevops/#at-the-group-l... ). This will disable it for all projects u
2.
by dgruesso 7y ago
GitLab PM here. Auto DevOps makes use of herokuish in order to find the language of your project. Herokuish images are Ubuntu-based, and it doesn't allow the use of specialized images. One can always provide a dockerfile (based on the
3.
by dgruesso 7y ago
Hi jbergstroem. GitLab PM here. thanks for the feedback. Our vision is indeed ambitious and we recognize that not all of our categories are yet "complete" (more on our category maturity here https://about.gitlab.com&#x2
4.
by dgruesso 7y ago
Hi @sigi45, GitLam PM here. Thanks, I'm glad you like GitLab and have noticed the improvements we've been working on for Auto DevOps. I'm sorry things didn't work out of the box for you, we've worked to cover many u
5.
by dgruesso 8y ago
Hi bvm, GitLab PM here. Sorry to hear your dev cluster broke. Would like to offer any help we can provide and if possible learn more about the failure so we can take corrective action to avoid this in the future. Thanks.
6.
by dgruesso 8y ago
Hi, GitLab PM here, thanks for the mention. We're indeed trying to make use of kubernetes inside GitLab as simple as possible. And just to add to your comment, you can try out kubernetes integration ( https://docs.gitlab.com&
7.
by dgruesso 8y ago
Thanks for the feedback Don. For your particular use case, you could use the same cluster for multiple environments if you have separate namespaces and use separate service accounts for each. Using RBAC will further ensure you don't ha
8.
by dgruesso 8y ago
Hi ratiolat, another GitLab PM here. Thanks for the feedback, as jl-gitlab mentioned, we'll work to make that clearer. You can think of Auto DevOps as a CI template that has a job for all devops stages built-in. If you want to experime