GitLab Acceleration Initiative meeting on 12 July, 2023

Created on 12 July 2023, 12 months ago
Updated 3 January 2024, 6 months ago

This meeting:
➤ Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.
➤ Usually happens every other Wednesday at 11:00 PT / Thursday 06:00 UTC
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Lots of threads get posted all at once! Don't worry - start at the top and then jump into the threads that most interest you.
➤ Has a public agenda anyone can add to in the issue
➤ *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

ping: @mixologic @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)

Transcript

0️⃣ Who is here today? Comment in the thread below to introduce yourself!

1️⃣ Do you have any topics to propose for the meeting today? Feel free to propose them in this thread, and then I will give them their own unique threads for discussion. Conversation moving slow? Go ahead and open your own thread in the next numeric order.

2️⃣ GitLab CI

2️⃣ 1️⃣ Performance improvementsDone: Using apache from our image: #3372464: Improve apache usage  (edited) 

2️⃣ 2️⃣ ConcurrencyAn optional variable is now available to allow running tests with concurrency for even more speed:https://drupal.slack.com/archives/CGKLP028K/p1689066316386919[#3370952] (edited) 

2️⃣ 3️⃣ Performance testing for coreThere is an effort underway to get OpenTelemetry to measure Drupal core performance: [#3352459]per @catchGitLabCI is enabled for core - so this could be setup as a separate scheduled pipeline. It does not need to wait for the rest of core testing to migrate. (edited) 

2️⃣ 4️⃣ More support for Drupal core testing on GitlabCICc @larowlan - do you have a list of blockers that could use DA support to move forward? (edited) 

3️⃣ GitLab Issues

3️⃣ 1️⃣ Issue summary update for roadmap to enabling issue migrationThis is still a todo for me, I've been pulled into some other major things. Will work on soon.

3️⃣ 2️⃣ Migration code for issues - in good shape on dev

3️⃣ 3️⃣ Migration code for credit/credit content type in D9 - in good shape on dev.

3️⃣ 4️⃣ Dependencies:A full D9/d10 migration of d.o is not required for the issue migration, however portions were built in D9, and we're using SSO and a CDN strategy to migrate only individual pieces and not be blocked on the whole thing.This is also necessary for the project browser project, so it aligns from a prioritiy point of view.

4️⃣ CommunicationI still need to publish a broader announcement about GitLab CI I think..

Participants:

fjgarlin, larowlan, mstrelan

🌱 Plan
Status

Fixed

Component

Meeting

Created by

🇺🇸United States hestenet Portland, OR 🇺🇸

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

Comments & Activities

Production build 0.69.0 2024