Contrib.social

Determine if we should use GitLab CI

Open on Drupal.org →
Created on 31 October 2022, over 1 year ago
Updated 8 December 2023, 7 months ago

Problem/Motivation

We could run our tests on gitlab CI instead of drupalCI. I talked to drumm and he has opted this project in

There are 2 advantages to this

  1. We might be able to switch the file copier that Composer Stager uses in to the rsync copier. Right now rsync is not available on drupalci. this would mean we could actually test our build tests using rysnc.
  2. Using gitlab ci might be able to help with our build tests run faster. Right now build tests all make a copy of core clone to setup composer repos to use. Would be able to do this 1x for all of our build tests if we could make an artifact at the beginning for test run that all of our build test could use? If so then we could do this task just once.

Steps to reproduce

Proposed resolution

  1. Determine when Drupal core is likely to be using Gitlab CI. If this is before we are likely to get into core, 10.1 hopefully, then it probably make sense for us to do this switch. If core will still be using DrupalCI until after 10.1 it might not make sense for us to switch

We should probably figure this out before we take any other steps

We could check on ✨ Convert to GitLab CI Postponed and see if Project Browser has considered the core timing since they are also hoping to get into core by 10.1(I think)

Remaining tasks

User interface changes

API changes

Data model changes

🌱 Plan
Status

Closed: duplicate

Version

3.0

Component

Code

Created by

🇺🇸United States tedbow Ithaca, NY, USA

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024