Optimizing GH actions, to use less minutes. (WIP)

.github/workflows/ci-tests.yml

@@ -5,7 +5,27 @@ env:
   PHP_VERSION: 8.1
   COMPOSER_VERSION: v2
 
+# Detect if this action is already running, and cancel it.
+# This most likely happened because a second push has been made to a branch.
+concurrency:
+  group: ${{ github.repository_id }}-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
+  BranchNameLength:
+    name: Check branch length
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Ensure branch name length
+        uses: lekterable/branchlint-action@2.1.0
+        if: github.ref_type == 'branch' || github.ref_type == 'pull_request'
+        with:
+          allowed: |
+            /^.{1,100}$/
+          errorMessage: 'Branch name too long. This cannot be deployed to Lagoon.'
+
   ValidateComposer:
     name: Validate Composer
     runs-on: ubuntu-latest

.github/workflows/lagoon-tests.yml

@@ -0,0 +1,16 @@
+---
+name: "Tests of deployment"
+
+on:
+  deployment_status
+
+# @todo - this action does nothing useful right now, but it is to show that
+# the site URL is available as part of deployment_status.
+jobs:
+  tests:
+    if: github.event.deployment_status.state == 'success'
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "$URL"
+        env:
+          URL: ${{ github.event.deployment_status.target_url }}

.lagoon.yml

@@ -4,9 +4,21 @@ project: dpl-cms-core
 
 ssh: 20.238.147.183:22
 api: https://api.lagoon.dplplat01.dpl.reload.dk/graphql
+environment_variables:
+  git_sha: 'true'
 
 tasks:
   post-rollout:
+    - run:
+        name: Create new GH deployment
+        command: |
+          # @TODO Where can i place the token as a secret?
+          export GH_DEPLOYMENT_TOKEN = 'XXX';
+          export GH_DEPLOYMENT_ID = $(curl -L \
+            -X POST \
+            -H "Authorization: Bearer $GH_DEPLOYMENT_TOKEN" \
+            https://api.github.com/repos/danskernesdigitalebibliotek/dpl-cms/deployments \
+            -d '{"ref":"$LAGOON_GIT_SHA","description":"Triggered by Lagoon"}');
     - run:
         name: If drupal is not installed
         command: |
@@ -92,7 +104,19 @@ tasks:
           set -e
           drush en -y dpl_example_content
         service: cli
+    # @TODO How do we run this, even if something has gone wrong?
+    - run:
+        name: Setting Deployment status
+        command: |
+          # @TODO How do we set this to 'failure', if something has gone wrong?
+          DEPLOYMENT_STATUS="success";
 
+          DRUPAL_URL=$(drush browse);
+          export GH_DEPLOYMENT_ID = $(curl -L \
+            -X POST \
+            -H "Authorization: Bearer $GH_DEPLOYMENT_TOKEN" \
+            https://api.github.com/repos/danskernesdigitalebibliotek/dpl-cms/deployments/$GH_DEPLOYMENT_ID/statuses \
+            -d '{"environment":"$LAGOON_GIT_SHA","state":"$DEPLOYMENT_STATUS", "target_url":"$DRUPAL_URL"}');
 environments:
   main:
     cronjobs: