547 posts
On October 5, 2022, still during the National Day holiday, MacWk — the Mac cracked-software site — went offline. I'm in the official Telegram channel too, where everyone was muted. Word from all sides is that it went broke.
Today is the last day of the JH GitLab JIHULAB 101 creator camp. As my closing piece, let me share my story with JH and my experience using the JH GitLab SaaS platform.
This feature was proposed by JH and merged into GitLab via an MR. Shipped with JH GitLab 15.4, it brings support for another product Chinese teams actually use. Nice!
My company has a persistent headache: a large org with a mixed population and scattered knowledge often ends up with several teams building several applications for the same thing across several projects. Take workflow engines — we have three of them, functionally more or less identical, each developed separately by a different team on a different project.
Are you obsessed with pipeline performance, always looking for ways to speed it up? JH GitLab 15.2 already supports configuring image pull policies! The keyword is pull_policy.
JH GitLab 15.3 added a new feature: JSON-based tables that support filtering and sorting, making your tables dynamic and several times more useful.
This event runs on the JH GitLab SaaS platform, where you submit Issues to take part. Once an issue passes review, an admin labels it 101::DONE. I started wondering how to count how many each person passed, so I could tell early whether I'd won the Most Diligent Little Bee award.
If you found this article, you're probably a tech enthusiast or a geek. DevOps has become standard these days — every project needs automation — and running automated operations on GitLab is inseparable from the Runner that executes them. So why did I bring a JH GitLab Runner home?
First, a disclaimer: this method exploits a quirk that isn't a vulnerability, which the official team may patch at any time, breaking it. Before JH GitLab SaaS launched I already reported it to them: https://jihulab.com/gitlab-cn/saas-feedback/-/issues/10. It seems harmless enough that it was left as-is, which means we can use this non-vulnerability vulnerability to do something.
While taking part in the JH GitLab JIHULAB 101 creator camp, I noticed JH GitLab officially runs a bot that serves people in issues. It got me thinking: tons of places have auto-replying support bots — could I build one on JH GitLab just for fun?
