Gitlab: “required pipeline” moved from Premium to Ultimate tier in version 15

gitlab.com

33 points·deng··6 comments

Before folks panic, this is not about requiring test results to pass to merge in a repo, but rather requiring a particular CI job/config to be in all repos on the server.

It's questionable that they are moving this up a tier, but this feature really does seem like it makes the most sense as a compliance feature and all compliance features are 'Ultimate' already. Any other usage seems like it could be replaced by adding an 'include' directive to the relevant jobs.

Approval rules are also arguably a "compliance feature". If they moved those up to Ultimate, I think they'd be making Premium useless for many teams.

I don't think this is a biggie. It could probably be worked around with a CODEOWNERS over .gitlab-ci.yml.

> One of my customers has concerns with not only losing this specific Premium content but how often this up-tier motion will occurr going forward.

I would coin this "the cost of non-free". Many SaaS contracts are open to bait and switch by exploiting vendor lock-in. Just as gitlab did when they removed a pricing tier a while back.

Gitlab’s entire history is bait and switch and wrapping existing features into more expensive tiers.

It’s a complete disservice to recommend Gitlab to someone if an alternative is available.

They also push features down into lower cost tiers pretty regularly.

I don’t think either of your statements is true.

In fact, I think that gitlab’s very open development process is a strong reason to recommend them over available alternatives.

Reply on news.ycombinator.com