-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathsimulate-environment-reporting-dev.yml
More file actions
39 lines (33 loc) · 1.26 KB
/
simulate-environment-reporting-dev.yml
File metadata and controls
39 lines (33 loc) · 1.26 KB
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
name: Report development snapshot
# On a normal setup the backend and frontend built in the two build jobs would
# deploy the two artifacts to a server, and we would have set up reporting
# of the environment to kosli. In this example we do not have a server so
# we just simulate that we have deployed to development
on:
schedule:
- cron: '55 * * * *' # Runs 5 minutes before the start of every hour
workflow_dispatch:
env:
# kosli commands picks up org, env, trail and api-token from these environment variables
KOSLI_ORG: "${{ vars.KOSLI_ORG }}"
KOSLI_ENV: "${{ vars.KOSLI_ENV_DEV }}" #jira-integration-example-dev
KOSLI_API_TOKEN: "${{ secrets.KOSLI_PUBLIC_API_TOKEN }}"
KOSLI_CLI_VERSION: "${{ vars.KOSLI_CLI_VERSION }}"
jobs:
report-snapshot:
name: Report development snapshot
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Kosli cli
uses: kosli-dev/setup-cli-action@v2
with:
version:
${{ vars.KOSLI_CLI_VERSION }}
- name: Report snapshot
run: |
mkdir -p running
cp -r apps/frontend running/
cp -r apps/backend running/
kosli snapshot paths ${{ env.KOSLI_ENV }} \
--paths-file server-paths-file.yml