Add GitLab CI

Added a basic config according to the: https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →

There is one failure: https://git.drupalcode.org/issue/jquery_update-3436897/-/jobs/1184955 (probably caused by some differences between GitlabCI and DrupalCI).

So figured it out. In GitlabCI MRs, the module installation path is following:

http://localhost/web/sites/all/modules/custom/jquery_update-X/...

Where X is the issue number (see the $CI_PROJECT_NAME variable and https://git.drupalcode.org/issue/jquery_update-3436897/-/jobs/1251211):

$ php symlink_project.php "$CI_PROJECT_NAME" 'sites/all/modules/custom'
Creating symlinks in /builds/issue/jquery_update-3436897/web/sites/all/modules/custom/jquery_update-3436897 pointing back to files in /builds/issue/jquery_update-3436897

And see also this https://issue.pages.drupalcode.org/-/jquery_update-3436897/-/jobs/125121...

127.0.0.1 - - [05/Apr/2024:11:54:54 +0000] "HEAD /web/sites/all/modules/custom/jquery_update-3436897/replace/jquery/1.12/jquery.min.js HTTP/1.1" 200 269 "-" "simpletest517467;1712318094;660fe68ee7f9a3.70564980;vmybAJuH-BBwQ-ZL9MB_E9DOKHAAdh8kXl31dUIPDJA"

So I updated the test condition a bit and now the pipeline is green - https://git.drupalcode.org/issue/jquery_update-3436897/-/pipelines/138686. I think this is ready, moving to NR. Thanks!

This looks great, thanks for fixing the test - turned out to be useful that we'd described what the URLs look like in the test env in the comments.

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