Contrib.social

Switch to Gitlab CI for automated testing

Open on Drupal.org →
Created on 5 January 2024, 12 months ago
Updated 23 January 2024, 11 months ago

Summary

Gitlab CI is now generally available for testing contributed module code. See https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →

Maintainer tasks

1. Add GitLab CI configuration for this project:

A. Go to https://git.drupalcode.org/project/url_embed and sign in.
B. Use the repository UI (not the Web IDE) to add a new file (+ icon).
C. Type the file name as .gitlab-ci.yml
D. You will be presented with the option to select a template, select the Drupal Association's template.gitlab-ci.yml from the top of the list.
E. Use the UI to complete the commit to the repository (i.e., do not create a merge request, etc.)
F. Confirm successful integration at https://git.drupalcode.org/project/url_embed/-/pipelines

2. From this module's "Automated Testing" tab, click "Edit" for the existing Drupal CI test, then "Remove"
3. From this module's "Edit" tab, click the "Issues" tab and populate the "Custom issue summary template" with the following:

<h3 id="summary-problem-motivation">Problem/motivation</h3>

<h3 id="summary-steps-reproduce">Steps to reproduce</h3>
<ol>
  <li>Go to...</li>
  <li>Click on...</li>
  <li>Observe [describe the expected and actual output]</li>
</ol>
        
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
        
<div class="note-warning">This module uses Gitlab CI for automated testing of proposed code changes. To contribute code changes, create a merge request. Patch files will not trigger automated testing and are not sufficient for review.</div>
📌 Task
Status

Fixed

Version

2.0

Component

Code

Created by

🇺🇸United States mark_fullmer Tucson

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