Contrib.social

GitLab Acceleration Initiative meeting on 31 May, 2023

Open on Drupal.org →
Created on 17 May 2023, about 1 year ago
Updated 14 June 2023, about 1 year ago

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️⃣ All things GitLab and DrupalCon

2️⃣ 1️⃣ Contribution room activities!Help people set up GitLab CI using the templateUpdate documentationWork on template improvementsWork on the improvements described in 3️⃣  below(edited)

3️⃣ GitLab CI

3️⃣ 1️⃣ GitLab CI - General AvailabilityWe are still looking to get this enabled for all projects - could get the pieces together today, more likely to actually start it tomorrow - trying to dot all the i's and cross the t's@drumm may be able to speak to this further. (edited) 

3️⃣ 2️⃣ GitLab CI variable reviewAnyone able/willing to check if our variables include file is currently up to date with the current release /dev versions of Drupal and supported environments?https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/include...

3️⃣ 3️⃣ Usage monitoring/resource monitoringShort term:We are going to set some billing alarms and probably a monthly minute limit on at least a temporary basis - though that's a global setting across all projectsMid-term:Need to write more monitoring for this on a per project level.

3️⃣ 4️⃣ Testing non-default branches.Right now, testing is configured against the 'default' branch set in GitLab CI project settings.However, it's very common for projects to have multiple release branches.With some clever regex, we can hopefully set up to test branches named in common release branch patterns.

3️⃣ 5️⃣  Add logic to gitlab-ci.yml workflow to attempt to not duplicate all of the automated test triggers in a fork, we just want manual tests and MR testing.Maybe we can do something clever based on fork name or group or something.

3️⃣ 6️⃣  Enabling testing in the forks (edited) 

3️⃣ 7️⃣ Getting core testing working in a reasonable time frame (edited) 

3️⃣ 8️⃣ Legacy D7 testing support (edited) 

4️⃣ GitLab - Contribution Credit and Fork ManagementWith GitLab CI much closer to the finish line, the other big piece is migrating and enabling issue workflows.We had two big pieces to solve:Contribution creditFork/MR management and permissionsFran has been building a prototype solution of a bot that gives the user the tools to handle all of these things:https://drive.google.com/file/d/1P58l1_dquYXu3v6l1bvDjqIm3uWjvX_d/view?u... would unblock the permissions concerns with our collaborative workflow.

5️⃣ Personal Access Tokens@fjgarlin has been diving into the permissions that PAT grant and checking against the list of what we've blocked.We haven't yet finished auditing all this to determine if it's all good.

6️⃣ Feature request - per @markdorisonDo we think it’s going to be possible to automate the creation of “backport” merge requests? I have seen this done using GitHub Actions, but I am not as familiar with GitLab CI.

Participants:

markdorison, Björn Brala (bbrala), hestenet, drumm, FeyP, Juraj Nemec, marvil07, fjgarlin, moshe, cmlara, larowlan, Nick_vh, Gábor Hojtsy

🌱 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