Skip to content

Run Ruby 2 for merge requests in older stable branches

Lin Jen-Shin requested to merge run-ruby2-for-mr-targeting-stable-branch into 15-9-stable-ee

What does this MR do and why?

Run Ruby 2 for merge requests in older stable branches

We need this because the current stable branches still run on Ruby 2, addressing &5149 (comment 1312090598)

When we update the Ruby versions for stable branches to be the same Ruby version as the merge request, we can probably drop this.

However, I started to wonder, while this does address the current concern, for future Ruby upgrade we might need to change a lot of these rules again. The current workflow is too complex and not flexible at all.

I think we need to rework the whole workflow. For example, we shouldn't have special rules for Community contribution. That rule will not work for merge requests having pipeline:run-in-ruby2 or if it's targeting stable branches. If we want to apply the same fix, then we'll have to duplicate the rules for all the combinations, that's too difficult to maintain and clearly not fully working right now.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Lin Jen-Shin

Merge request reports