Problem/Motivation

The transition to GitLab CI is currently being tested. #3261803: Using GitLab CI instead of Drupal CI

Proposed resolution

Configure GitLab CI for testing.

Issue fork youtube-3357190

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

markdorison created an issue. See original summary.

markdorison’s picture

Assigned: markdorison » Unassigned
Status: Active » Needs work
jonathan1055’s picture

Hi,
I see that your new GitLab Ci run failed in the first composer step with

uploading artifacts...
/builds/project/youtube: found 63094 matching files and directories 
.git/**/*: excluded 48 files                       
.git: excluded 1 files                             
ERROR: Uploading artifacts as "archive" to coordinator... 413 Request Entity Too Large  id=44713 responseStatus=413 Request Entity Too Large status=413 token=64_UfRcN
FATAL: too large       

I have just added the gitlab-ci.yml to Scheduler and the job fails exactly like YouTube. See #3356800: Enable GitLab CI testing. I have raised this in the Drupal Slack gitlab channel, thinking it was an error in my project, but it might be a common thing.

markdorison’s picture

Status: Needs work » Needs review

GitLab CI now passing.

markdorison’s picture

StatusFileSize
new66.19 KB

Tests passing as expected.

screenshot of tests passing

  • markdorison committed e1d6017b on 2.x
    Issue #3357190 by markdorison, jonathan1055: Configure GitLab CI
    
markdorison’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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