Contrib.social

GitLab Acceleration Initiative meeting on 28 Jun, 2023

Open on Drupal.org →
Created on 28 June 2023, 11 months ago
Updated 3 January 2024, 5 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 CIWe've had some good adoption since the announcement of availability at DrupalConWe're getting a bit over 400 pipelines executed per week right now.

2️⃣ 1️⃣  GitLab CI - PerformanceA general concern is still that GitLabCI runs are noticeably slower than DrupalCI runs, not just in core, but also in some apples to apples contrib examples. This is something that @fjgarlin has been looking at a bit - but would also be a good area of contribution for anyone who has experience optimizing CI in GitLab.Is there any way to replicate tmpfs style optimizations from DrupalCI in GitLabCI without 'hacking' the runner? (edited) 

2️⃣ 2️⃣ GitLab CI for CoreSpeaking of which - it would be good to continue supporting the work of folks trying to get core running.

3️⃣ GitLab issuesThis is our next big milestone, and frankly is what lets us fully realize the vision of getting everything moved to GitLab.We demoed a fork management option - and got your feedback on two areas:Trying to make sure that as much of the GitLab UI is usable as expected (someone trying to click a fork button when browsing a module, etc) Trying to limit the amount of back and forth needed between a d.o node and the GitLab issues - which are hopefully only needed as an access management step.

3️⃣ 1️⃣ Truthfully though, our next big blocker before we see much more progress on this is actually our SSO work for the D7->D10 upgrade for D.O - because that is what will let us migrate credit, and implement these access management workflows.This is our next highest priority after the work we're doing for #autoupdates on the secure signing server.

Participants:

Björn Brala (bbrala), markie, markdorison, hestenet, andypost, fjgarlin, drumm, moshe

🌱 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

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024