4
4
pull_request :
5
5
6
6
jobs :
7
- leia-tests :
7
+ leia-test :
8
8
runs-on : ${{ matrix.os }}
9
9
env :
10
10
TERM : xterm
11
11
strategy :
12
12
matrix :
13
- leia-tests :
13
+ leia-test :
14
14
- examples/mariadb-10.0
15
15
- examples/mariadb-10.1
16
16
- examples/mariadb-10.2
17
17
- examples/mariadb-10.3
18
18
- examples/mariadb-10.4
19
19
# This is known to not work and uses a later image
20
20
# - examples/mariadb-10.5
21
- lando-versions :
22
- - edge
21
+ lando-version :
22
+ - 3-dev-slim
23
23
os :
24
24
- ubuntu-22.04
25
25
node-version :
26
- - ' 16 '
26
+ - ' 18 '
27
27
28
28
steps :
29
29
# Install deps and cache
@@ -33,43 +33,28 @@ jobs:
33
33
uses : actions/setup-node@v2
34
34
with :
35
35
node-version : ${{ matrix.node-version }}
36
- cache : yarn
37
- - name : Install Yarn dependencies
38
- run : yarn install --prefer-offline --frozen-lockfile
39
-
40
- # This block should eventually become use lando/actions-hyperdrive@v2
41
- - name : Verify Docker dependencies
42
- run : |
43
- docker --version | grep "20.10."
44
- docker-compose --version | grep "1.29."
45
- - name : Grab latest edge Lando CLI
46
- run : |
47
- sudo curl -fsSL -o /usr/local/bin/lando "https://files.lando.dev/cli/lando-linux-x64-${{ matrix.lando-versions }}"
48
- sudo chmod +x /usr/local/bin/lando
49
- - name : Move in lando config appropriate for testing
50
- run : |
51
- mkdir -p ~/.lando/cache
52
- cp -f actions-lando-config.yml ~/.lando/config.yml
53
- echo false > ~/.lando/cache/report_errors
54
- lando --clear
55
- - name : Verify Lando works and we are dogfooding this plugin for tests
56
- run : |
57
- lando version
58
- lando config --path plugins | grep platformsh | grep /home/runner/work/platformsh/platformsh || (echo "::error:: Not dogfooding this plugin correctly!" && exit 1)
59
- cd ${{ matrix.leia-tests }}
60
- lando config --path plugins | grep platformsh | grep dir | grep /home/runner/work/platformsh/platformsh || (echo "::error:: Not dogfooding this plugin correctly!" && exit 1)
61
-
62
- # This block should eventually become use lando/actions-leia@v2
63
- # @NOTE? Do we want a way for our leia-action to configure apparmor since
64
- # this might break a whole bunch of tests? or is this literally just a thing
65
- # for the platform.sh mysql/mariadb container?
66
- - name : Configure apparmor
67
- run : |
68
- set -x
69
- sudo apt-get remove mysql-server --purge
70
- sudo apt-get install apparmor-profiles
71
- sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.mysqld
72
- - name : Run leia tests
73
- shell : bash
74
- run : yarn leia "./${{ matrix.leia-tests }}/README.md" -c 'Destroy tests' --stdin --shell bash
36
+ cache : npm
37
+ - name : Install NPM dependencies
38
+ run : npm clean-install --production --prefer-offline --frozen-lockfile
75
39
40
+ - name : Bundle Deps
41
+ uses : lando/prepare-release-action@v3
42
+ with :
43
+ lando-plugin : true
44
+ version : dev
45
+ sync : false
46
+ - name : Setup lando ${{ matrix.lando-version }}
47
+ uses : lando/setup-lando@v2
48
+ with :
49
+ lando-version : ${{ matrix.lando-version }}
50
+ config : |
51
+ setup.skipCommonPlugins=true
52
+ setup.plugins.@lando/platformsh=/home/runner/work/platformsh/platformsh
53
+ telemetry : false
54
+ - name : Run Leia Tests
55
+ uses : lando/run-leia-action@v2
56
+ with :
57
+ leia-test : " ./${{ matrix.leia-test }}/README.md"
58
+ cleanup-header : " Destroy tests"
59
+ shell : bash
60
+ stdin : true
0 commit comments