Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jl-gitlab
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
jl-gitlab
8y ago
Hey there, product manager at GitLab for review apps here. I'd love to hear about the warts that you ran into that caused you to move to k8s. We're always working on improving the product and feedback like yours is really the most
32.
▲
by
jl-gitlab
8y ago
If you have any advice or learnings for us, feel free to jump into that issue. :)
33.
▲
by
jl-gitlab
8y ago
CI/CD product manager from GitLab here. We're actually already looking at adding this - we're starting with some experimentation in our internal item at https://gitlab.com/gitlab-com/gl-infra/infrast
34.
▲
by
jl-gitlab
8y ago
The very next thing you teach them after the theoretical knowledge of how the pieces move is to sit on their hands, to avoid making impulsive moves.
35.
▲
by
jl-gitlab
8y ago
No worries, I understand how you could come to that conclusion. I've opened up an issue to see if we can make that more clear: https://gitlab.com/gitlab-org/gitlab-ce/issues/52144
36.
▲
by
jl-gitlab
8y ago
The documentation link you shared was for AutoDevOps, a different (but related) feature from CI/CD. It's a build and deployment solution specifically for Kubernetes/Containers, which is why it has those requirements. GitLab C
37.
▲
by
jl-gitlab
8y ago
Hey there, I'm the product manager for CI/CD at GitLab. AutoDevOps is one of our more advanced features to get up and running in a k8s environment quickly, but is not required if you just want basic CI. Our documentation on gettin
38.
▲
by
jl-gitlab
8y ago
Interesting idea. We already sort of have a special-case MR (WIP) where merge is disabled until the work-in-progress status is removed. It could be interesting to have an RFC equivalent where no merge is clearly ever intended, but you still
39.
▲
by
jl-gitlab
8y ago
Thanks for the feedback, that's awesome to hear!
40.
▲
by
jl-gitlab
8y ago
Hey, PM at GitLab for CI/CD here. We're making a lot of investments in both the infrastructure supporting gitlab.com as well as the functionality and reliability of the CI pipelines themselves, including looking at intermittent is
41.
▲
by
jl-gitlab
8y ago
To add on, we are actively working on balancing how we deliver new and deep solutions, CI in particular is an area where we want to provide better solutions for more complex problems (as well as address some of the challenges like hung buil
42.
▲
by
jl-gitlab
8y ago
Really sorry to hear you've had that experience. I'm the PM for CI and we're really proud of how our CI product in particular has been rated by industry analysts, and how we've maintained interoperability, though of cour