Configure GitLab CI

Created on 6 December 2023, about 1 year ago
Updated 12 December 2023, about 1 year ago

Problem/Motivation

Drupal is moving to using GitLab CI, let's be proactive and start moving ourselves.

https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... β†’

Remaining tasks

Add gitlab ci configuration file
Check that it works and runs our tests.

User interface changes

None

API changes

None

Data model changes

None

✨ Feature request
Status

Active

Version

2.1

Component

Code

Created by

πŸ‡ͺπŸ‡ΈSpain manuel garcia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @manuel garcia
  • πŸ‡¬πŸ‡§United Kingdom oily Greater London

    andrew.farquharson β†’ made their first commit to this issue’s fork.

  • πŸ‡¬πŸ‡§United Kingdom oily Greater London
    1. I add a .gitlab-ci.yml file to the project root using the contents of the Drupal Association's template.gitlab-ci.yml.
    2. Committed the file to the issue branch
    3. On commit the pipeline was triggered automatically and ran the tests
    4. The PHPUnit tests terminated with one failure.

    I think a new issue should be created to fix the failing test.

    Further investigation of the test failure can be carried out under this ticket to make sure that the failure is due to a test error: that the tests have reported the error correctly. That is proof that the pipleline is working correctly.

  • Status changed to Needs review about 1 year ago
  • πŸ‡¬πŸ‡§United Kingdom oily Greater London
  • Status changed to Postponed about 1 year ago
  • πŸ‡ͺπŸ‡ΈSpain manuel garcia

    Thanks, I'm learning about this as I go, but as far as I can tell the build failed with:
    Unable to install modules: module 'view_profiles_perms_test' is incompatible with this version of Drupal core. - and its using Drupal version : 10.1.8-dev

    So indeed this is a bug, we (I) forgot to upgrade to Drupal 10 the module we use in the test to setup things.

    I've created πŸ› view_profiles_perms_test not compatible with Drupal 10 Fixed for the same, postponing this until we get that fixed, so we can get tests actually running on Gitlab.

  • πŸ‡¬πŸ‡§United Kingdom oily Greater London

    @Manuel Ah, that makes sense.

  • Status changed to Active about 1 year ago
  • πŸ‡ͺπŸ‡ΈSpain manuel garcia

    We now have a passing 2.1.x branch, so we can proceed with this.

  • πŸ‡¬πŸ‡§United Kingdom oily Greater London

    Hi @Manuel Garcia, I am not sure if the gitlab configuration just needs to work for Drupal 10 and if not which versions of Drupal core the tests need to be tested on.. Also does the gitlab configuration it the .gitlab-ci.yml just need to be compatible with the 2.1.x branch or with other branches also?

  • Merge request !72.1.x β†’ (Open) created by oily
  • Open in Jenkins β†’ Open on Drupal.org β†’
    Core: 10.1.x + Environment: PHP 8.2 & MySQL 8
    last update about 1 year ago
    1 pass
  • πŸ‡ͺπŸ‡ΈSpain manuel garcia

    Let's bring in the phpstan.neon file from the PR we worked on for πŸ› view_profiles_perms_test not compatible with Drupal 10 Fixed , it should take care of this warning: https://git.drupalcode.org/issue/view_profiles_perms-3406407/-/jobs/475158

    Re @andrew.farquharson #8

    Hi @Manuel Garcia, Since branch 2.1.x has core compatibility with Drupal 9 and 10 I am not sure if the .gitlab-ci.yml needs to be edited to test on Drupal 9 and 10 versions? I imagine that the scope of this ticket is to make changes only to the .gitlab-ci.yml. The functional test is now fixed so it should work on Drupal 9 and 10, now? Is there anything i am missing?

    I'm not entirely sure if we need to customize our .gitlab-ci.yml file to be honest, I had a read of https://www.drupal.org/node/3356364 β†’ and couldnt figure it out. You are right in that we should be testing with both supported Drupal core versions though.

Production build 0.71.5 2024