GitLab Acceleration Initiative meeting on 20 Sept, 2023

Created on 6 September 2023, about 1 year ago
Updated 3 January 2024, 11 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 18: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 CIAlso some DrupalCI_Environments issues (still used by Gitlab CI) in this top level thread (edited) 

2️⃣ 1️⃣ CI for Modern CoreTruly incredible progress in the last couple weeks especially. We are looking at the possibility of sub-10-minute core runs.Meta issue: 📌 Investigate realistic resource requests for core jobs Active (edited)

2️⃣ 2️⃣ CI for Drupal 7 CoreMR in Needs Review: 📌 [D7] GitLab CI integration for core Needs review  (edited) 

2️⃣ 3️⃣ CI for Modern contrib -- this has already been 'done' for a while - may benefit from some improvements we are finding.

2️⃣ 4️⃣ CI for D7 contrib - A template for CI for D7 contrib has been proposed here: https://drupal.slack.com/archives/CGKLP028K/p1695227405485629 (edited) 

3️⃣ GitLab InfrastructureIncreased usage has exposed performance issues.The concurrency limit in GitLab config was set/raised.One issue is already (mostly) resolved - excessive redirects: https://drupal.slack.com/archives/C51GNJG91/p1695140980564319Our GitLab1 needs a migration from OSU OSL to AWS alongside GitLab-aws - we are working on a staging cluster to validate that geo replication will survive the transition. (edited)

4️⃣ GitLab Issues - we are making some progress on getting ready for the SSO work that enables the credit migration that enables the issue opt-in process.@heddn has been working with us on that, keycloak instance updated, rebasing/rerolling some issues etc.We won't have the sso migration/issue opt in switch before Lille, but I hope we can get to it as the next big push after we get back.With all the CI momentum I'm really feeling the energy to move this next. (edited) 

Participants:

andypost, hestenet, larowlan, poker10, bbrala, Wim Leers, markdorison, drumm

🌱 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.71.5 2024