Add gitlab CI

Prashant.c → made their first commit to this issue’s fork.

Incorporated a .gitlab-ci.yml file into the project's root directory by utilizing the Drupal Association's template.gitlab-ci.yml contents. Continuously learning about it as I progress.

Thanks

Thanks!
Could you please create a merge request so this can be tested? If the tests pass, I guess we can just merge this.

However, one important point is that we currently have automatic testing configured → for different setups – two tested weekly, and one for each patch, MR and commit. Is it possible to set up something like that in GitLab CI, too? I wouldn’t want to use actual functionality. (Could be a follow-up, though, before we disable the old DrupalCI tests.)

Hi @drunken-monkey,

Yes, in GitLab CI, we can configure automated testing for various setups similar to what we have with DrupalCI. We can utilize Scheduled pipelines and refer to https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... → .

drunken monkey → closed merge request !15

Good to know, thanks!
Merged. Thanks again!

Unfortunately, there seems to be some problem with the GitLab CI pipeline, which failed even though the DrupalCI tests all passed → . Maybe we need to manually start the chromedriver background process to allow JS tests to run?

I would actually have thought that d.o would show such a test failure in the issue, but apparently not – or maybe just not for the issue adding the .gitlabci.yml file? Otherwise, I wouldn’t have merged this, of course.
Anyways, we need to fix this before we can really switch to GitLab CI.

Also, side note: Do you know whether there is a way to still get notified via mail when a pipeline fails? That was a very important feature of DrupalCI, in my opinion.
In any case, thanks a lot again for your help!

It is possible that manually starting the chromedriver background process could serve as a solution . Upon closer look it seems tests runs differently between the legacy test bots and GitLabCI .

As for the notifications, GitLab does offer email notifications for pipeline failures. You can configure these notifications in your GitLab account settings under the Notifications section. Please refer to the following article Notification emails

OK, chromedriver does seem to be running (would have been very weird if not), but it’s started slightly differently apparently. By adding --no-sandbox to the chromedriver command I use locally, I could indeed reproduce this error.
No idea how to override the command used in GitLab CI, but let’s give it a try. Otherwise, I might need to adapt the test to pass instead. (Same if there is a good reason that this --no-sandbox flag is included.)

Thanks again for the other tips, very helpful!

Hm, no, that doesn’t seem to have been it, fails exactly the same way. But I’m not sure whether that’s because the CI didn’t pick up the changed chromedriver command or whether that just didn’t fix the issue. I also cannot find anywhere in the pipeline’s output the actual command used. Do you have any idea how I can check this?

vipin.mittal18 → made their first commit to this issue’s fork.

@vipin.mittal18: Could you please explain what you did and why?

Reverted your change, since it seemed detrimental. Also, I think I figured out why the test is failing. Fingers crossed.

GitLab CI is passing, and coding standards can be addressed separately.

There are still some phpstan issues that needs to be addressed before merging.
Setting the status back to NW

Merged.
Thanks again, everyone!

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