-
Notifications
You must be signed in to change notification settings - Fork 20
181 lines (148 loc) · 5.78 KB
/
Copy pathweekly.yml
File metadata and controls
181 lines (148 loc) · 5.78 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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
# Weekly tests to catch changes in upstream dependencies like pins
# that break vetiver e.g. changes in pins could break either one or
# both of:
# 1. pypi release
# 2. main branch version
name: Weekly Tests
on:
schedule:
- cron: "03 14 * * MON"
push:
branches: ['update-weekly']
jobs:
vetiver_main_pins_main:
name: 'vetiver main, pins main'
if: github.repository == 'rstudio/vetiver-python'
runs-on: ubuntu-latest
strategy:
matrix:
# Minimum and Maximum supported versions
python-version: ['3.10']
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Install dependencies
run: |
python -m pip install --upgrade pip
python -m pip install '.[all]'
python -m pip install --upgrade git+https://github.com/rstudio/pins-python
- name: Run tests
run: |
make test
vetiver_pypi_pins_main:
name: 'vetiver pypi, pins main'
if: github.repository == 'rstudio/vetiver-python'
runs-on: ubuntu-latest
strategy:
matrix:
# Minimum and Maximum supported versions
python-version: ['3.10']
steps:
- name: Get latest release with tag from GitHub API
id: latestrelease
run: |
echo "::set-output name=releasetag::$(curl -s https://api.github.com/repos/rstudio/vetiver-python/releases/latest | jq '.tag_name' | sed 's/\"//g')"
- name: Confirm Release Tag
run: |
echo ${{ steps.latestrelease.outputs.releasetag }}
- name: Checkout Code
uses: actions/checkout@v3
with:
ref: ${{ steps.latestrelease.outputs.releasetag }}
- uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Install dependencies
run: |
python -m pip install --upgrade pip
python -m pip install .[dev]
python -m pip install --upgrade git+https://github.com/rstudio/pins-python
- name: Run Tests
run: |
make test
vetiver_pypi_rsconnect_latest:
name: 'vetiver pypi, rsconnect latest'
runs-on: ubuntu-latest
strategy:
matrix:
# Minimum and Maximum supported versions
python-version: ['3.14']
steps:
- name: Get latest release with tag from GitHub API
id: latestrelease
run: |
echo "::set-output name=releasetag::$(curl -s https://api.github.com/repos/rstudio/vetiver-python/releases/latest | jq '.tag_name' | sed 's/\"//g')"
- name: Confirm Release Tag
run: |
echo ${{ steps.latestrelease.outputs.releasetag }}
- name: Checkout Code
uses: actions/checkout@v3
with:
ref: ${{ steps.latestrelease.outputs.releasetag }}
- uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Install dependencies
run: |
python -m pip install --upgrade pip
python -m pip install .[dev]
python -m pip install --upgrade git+https://github.com/rstudio/rsconnect-python
- name: Run Connect integration tests
uses: posit-dev/with-connect@0783dabdd24e360e985a4588ce1239c3dc31c542
with:
license: ${{ secrets.RSC_LICENSE }}
command: |
pip freeze | grep -v '^vetiver' | grep -v '^-e ' > requirements.txt
echo 'vetiver' >> requirements.txt
pytest vetiver/tests/test_rsconnect.py -m 'rsc_test'
- name: Open issue on failure
if: failure() && github.event_name == 'schedule'
uses: actions/github-script@v7
with:
script: |
github.rest.issues.create({
owner: context.repo.owner,
repo: context.repo.repo,
title: `Weekly canary failed: ${context.job}`,
body: `The weekly Connect canary failed on run ${context.runId}. This often means a change in rsconnect-python \`main\` broke vetiver. See https://github.com/${context.repo.owner}/${context.repo.repo}/actions/runs/${context.runId}`,
labels: ["ci-failure"]
})
vetiver_latest_rsconnect_latest:
name: 'vetiver latest, rsconnect latest'
runs-on: ubuntu-latest
strategy:
matrix:
# Minimum and Maximum supported versions
python-version: ['3.9']
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Install dependencies
run: |
python -m pip install --upgrade pip
python -m pip install '.[all]'
python -m pip install --upgrade git+https://github.com/rstudio/rsconnect-python
- name: Run Connect integration tests
uses: posit-dev/with-connect@0783dabdd24e360e985a4588ce1239c3dc31c542
with:
license: ${{ secrets.RSC_LICENSE }}
command: |
pip freeze | grep -v '^vetiver' | grep -v '^-e ' > requirements.txt
echo 'vetiver' >> requirements.txt
pytest vetiver/tests/test_rsconnect.py -m 'rsc_test'
- name: Open issue on failure
if: failure() && github.event_name == 'schedule'
uses: actions/github-script@v7
with:
script: |
github.rest.issues.create({
owner: context.repo.owner,
repo: context.repo.repo,
title: `Weekly canary failed: ${context.job}`,
body: `The weekly Connect canary failed on run ${context.runId}. This often means a change in rsconnect-python \`main\` broke vetiver. See https://github.com/${context.repo.owner}/${context.repo.repo}/actions/runs/${context.runId}`,
labels: ["ci-failure"]
})