News for hackers. Stuff that matters.

A comment on GitHub incident – now resolved. Parent comment

Re:GitHub incident – now resolved by synu on Wednesday June 29, 2022 @11:59AM (#31922013)
Wow! I’ve heard GitLab CI is hard to learn because it’s so expansive, but never that it is non-existent. Do you mind sharing more?
[ Parent | on HN ]
Re:GitHub incident – now resolved by dnsmichi on Wednesday June 29, 2022 @12:45PM (#31922627)
GitLab team member here.

I'd recommend starting with one of the workshops listed here [0] and maybe dive into more learning resources and the documentation.

Our community platforms, such as the forum [2] and Stack Overflow, etc. [3] are also a great place to ask questions and collaborate on challenges.

[0] https://about.gitlab.com/handbook/marketing/community-relati...

[1] https://about.gitlab.com/learn/

[2] https://forum.gitlab.com/

[3] https://about.gitlab.com/community/

[ Parent | on HN ]
Re:GitHub incident – now resolved by bastardoperator on Wednesday June 29, 2022 @01:09PM (#31922933)
When I talk to Hashicorp or AWS they provide tooling specifically for GitHub Actions. I don't see the same level of vendor commitment when it comes to GitLab. If I'm not going to get vendor commitment I might as well run buildkite which is awesome or even look to something like Tekton for Kubernetes if I'm just doing Kubernetes anyways.
[ Parent | on HN ]
Re:GitHub incident – now resolved by synu on Wednesday June 29, 2022 @02:43PM (#31924127)
Gotcha, that makes sense. Thanks for replying.
[ Parent | on HN ]
Re:GitHub incident – now resolved by _joel on Wednesday June 29, 2022 @12:16PM (#31922228)
It's patently wrong there is no community, I've been part of it writing buildpacks.
[ Parent | on HN ]