Replace outdated DrupalCI testing in favor to new GitLab CI pipelines

Created on 19 October 2023, 8 months ago

Problem/Motivation

Since Jun 2023, Drupal.org enabled GitLab CI for testing purposes. GitLab CI is now preferred over DrupalCI for testing.
This issue is to track progress towards getting a .gitlab-ci.yml file so that we can migrate away from the deprecated DrupalCI to GitLab CI.

GitLab CI documentation: https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →

Benefits:

1) Testing is about five times faster
@see: https://www.drupal.org/about/core/blog/drupal-cores-gitlab-ci-testing-is... →

2) Ability to configure tests in a more obvious and flexible way.

3) Great UI!

API changes

No API changes.

✨ Feature request

Status

Fixed

Version

3.0

Component

Code

Created by

🇺🇦Ukraine abramm Lutsk

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @abramm
Open in Jenkins → Open on Drupal.org →
Core: 10.1.4 + Environment: PHP 8.1 & MySQL 5.7
last update 8 months ago
11 pass
@abramm opened merge request.

Comment 8 months ago →

System Message

abramm → committed e72bc11f on 3.0.x

Issue #3395239: Replace outdated DrupalCI testing in favor to new GitLab...

Status changed to Fixed 8 months ago12:14pm 19 October 2023
Comment 8 months ago →
🇺🇦Ukraine abramm Lutsk
Comment 8 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024