-
Notifications
You must be signed in to change notification settings - Fork 1
51 lines (48 loc) · 1.63 KB
/
node.js.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
name: Node.js CI
on:
push:
branches: ['main']
pull_request:
branches: ['main']
jobs:
build:
runs-on: [self-hosted, Linux, X64, marquinhos-ci]
strategy:
matrix:
node-version: [20.x]
steps:
- uses: actions/checkout@v3
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v3
with:
node-version: ${{ matrix.node-version }}
cache: 'npm'
- run: npm ci
- run: npm run build
deploy:
needs: build
runs-on: [self-hosted, Linux, X64, marquinhos-ci]
steps:
- name: Check if service exists
run: systemctl --user list-units --type=service --all | grep -q 'marquinhos-bot.service'
continue-on-error: true
id: check-service
- name: Stop service
if: steps.check-service.outputs.returncode == 0
run: systemctl --machine=marquinhos@localhost --user stop marquinhos-bot.service
- name: Copy service file
run: cp marquinhos-bot.service ~/.config/systemd/user/marquinhos-bot.service
- name: Reload systemd
run: systemctl --machine=marquinhos@localhost --user daemon-reload
- name: Start service
run: systemctl --machine=marquinhos@localhost --user start marquinhos-bot.service
- name: Check status
id: check-status
run:
if [ "$(systemctl --machine=marquinhos@localhost --user is-active marquinhos-bot.service)" != "active" ]; then
echo "Service is not running or has failed"
exit 1
fi
- name: Fail if service is not running
if: steps.check-status.outcome != 'success'
run: exit 1