Add gitlab CI

I have been meaning to do this but I admit it's a giant learning curve for me. If you've got the capacity to do more than plug the standard template in, I'd like to see:

• Remove all test runs for php <8.1
• Add tests for php 8.1 and 8.2
• Ensure functional tests are run - they're really important for this module
• Solve all script failures

I've added gitlab CI. Check it.

@bobi-mel I suspect you hadn't seen my comments in #4 before writing #5

Hi @darvanen

You're absolutely right. I have assigned the issue to me and have not refreshed the page. I'll change the gitlab Ci file and fix all errors.

Added a few comments for better future maintainability.

Hi @darvanen

Is it possible to create individual sub-tasks to solve script failures?

Thanks @bohart, good feedback.

@bobi-mel can you think of a way to complete those sub-tasks without committing the gitlab pipeline? I don't want to switch to gitlab until it is as green as the current automated test suite.

For instance, could we disable phpstan checks or reduce the level for this issue and create a follow-up to implement them and do the cleanup at the same time?

Why has this been set to 'needs review'? None of @bohart's comments have been addressed for starters.

I have made the D10 tests green, but I still maitnain that a parallel job with a matrix is unnecessary when the matrix only has one value. See how core does it on line 193+ of https://git.drupalcode.org/project/drupal/-/blob/11.x/.gitlab-ci.yml?ref...

It would be nice if someone addressed the cspell issues by ignoring the composer.json file and adding a few extra words to the dictionary. I've run out of time to figure out how to do that. Happy for it to be a follow-up instead.

Ok I finally went digging and learned how this stuff works properly. Turns out "OPT_IN_TEST_NEXT_MAJOR" from the template automatically tests the maximum version of PHP so we don't need any custom jobs to make that happen. We could use "OPT_IN_TEST_MAX_PHP" to *just* do PHP but I also want to support the next major.

I've also landed on an approach for this that I've used on two other modules so I'm updating the issue summary with that approach.

PHPStan is only failing on 'next major' so I'm happy to leave that one enabled since the current version one goes green.

Follow-ups:

📌 Add and configure ESLint to GitLab test runner. Needs work - existing, thanks @bobi-mel
📌 Fix and re-enable CSPell test Active
🐛 Drupal 11 PHPStan tests failing Active

Thanks everyone for your work on this! I've merged this and disabled the old CI on this module.

Added related issue links

Snuck the next_minor job in on this issue to avoid giving myself another credit for just one line.

Automatically closed - issue fixed for 2 weeks with no activity.