forked from MODFLOW-ORG/modflow6
-
Notifications
You must be signed in to change notification settings - Fork 0
413 lines (388 loc) · 19 KB
/
Copy pathrelease_dispatch.yml
File metadata and controls
413 lines (388 loc) · 19 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
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
name: MODFLOW 6 release dispatch
on:
push:
branches:
# initial phase of the release procedure is triggered by pushing a release branch, for
# a patch release (patch version 1-9, then anything) or a release candidate (ending in
# rc). A new minor release, vX.Y.0, needs its DOI as input so is started via dispatch.
- v[0-9]+.[0-9]+.[1-9]*
- v[0-9]+.[0-9]+.[0-9]+rc*
# intermediate phase is triggered by merging the release branch to master
- master
# final phase is triggered by promoting/publishing a GitHub release draft to a full release
release:
types:
- published
# workflow_dispatch trigger to start release via GitHub UI or CLI,
# as an alternative to triggering when a release branch is pushed.
# see https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
workflow_dispatch:
inputs:
branch:
description: 'Branch to release from.'
required: true
type: string
compiler_toolchain:
description: 'Compiler toolchain to use. For supported options see https://github.com/MODFLOW-ORG/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
required: false
type: string
default: 'intel-classic'
compiler_version:
description: 'Compiler version to use. For supported options see https://github.com/MODFLOW-ORG/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
required: false
type: string
default: '2021.6'
releasemode:
description: 'Build a full distribution containing sources, examples, and all documentation. If false, the distribution contains only binaries, mf6io, release notes, and code.json, with binaries built in develop mode, and disclaimers & version strings indicating preliminary/provisional status. If true, a full distribution is created, with binaries built in release mode, and disclaimer language indicating review and approval.'
required: false
type: boolean
default: false
run_tests:
description: 'Run tests after building binaries.'
required: false
type: boolean
default: true
version:
description: 'Version number to use for release.'
required: true
type: string
patch:
description: 'Create a patch release. If true, only bug fixes and new examples will be included in generated documentation.'
required: false
type: boolean
default: false
doi:
description: 'DOI link of the release, e.g. https://doi.org/10.5066/P1PGE9XW, for the release history in the release notes. Required for a new minor or major release unless its release history row was already added to the release branch. Patch releases reuse the DOI of the previous release with the same major and minor version.'
required: false
type: string
jobs:
set_options:
name: Set release options
if: github.event_name != 'release' && github.ref_name != 'master'
runs-on: ubuntu-22.04
defaults:
run:
shell: bash -l {0}
outputs:
branch: ${{ steps.set_branch.outputs.branch }}
compiler_toolchain: ${{ steps.set_compiler.outputs.compiler_toolchain }}
compiler_version: ${{ steps.set_compiler.outputs.compiler_version }}
version: ${{ steps.set_version.outputs.version }}
patch: ${{ steps.set_patch.outputs.patch }}
date: ${{ steps.set_date.outputs.date }}
steps:
- name: Checkout modflow6
uses: actions/checkout@v7
with:
repository: ${{ github.repository_owner }}/modflow6
ref: ${{ github.ref }}
- name: Set branch
id: set_branch
run: |
# if branch was provided explicitly via workflow_dispatch, use it
if [[ ("${{ github.event_name }}" == "workflow_dispatch") && (-n "${{ inputs.branch }}") ]]; then
branch="${{ inputs.branch }}"
# prevent releases from master
if [[ "$branch" == "master" ]]; then
echo "error: releases may not be triggered from branch $branch"
exit 1
fi
echo "using branch $branch from workflow_dispatch"
elif [[ ("${{ github.event_name }}" == "push") && ("${{ github.ref_name }}" != "master") ]]; then
# if release was triggered by pushing a release branch, use that branch
branch="${{ github.ref_name }}"
echo "using branch $branch from ref ${{ github.ref }}"
else
# otherwise exit with an error
echo "error: this workflow should not have triggered for event ${{ github.event_name }} on branch ${{ github.ref_name }}"
exit 1
fi
echo "branch=$branch" >> $GITHUB_OUTPUT
- name: Set compiler
id: set_compiler
run: |
# if compiler toolchain was provided explicitly via workflow_dispatch, use it
if [[ ("${{ github.event_name }}" == "workflow_dispatch") && (-n "${{ inputs.compiler_toolchain }}") ]]; then
compiler_toolchain="${{ inputs.compiler_toolchain }}"
compiler_version="${{ inputs.compiler_version }}"
echo "using compiler toolchain $compiler_toolchain version $compiler_version from workflow_dispatch"
elif [[ ("${{ github.event_name }}" == "push") && ("${{ github.ref_name }}" != "master") ]]; then
# if release was triggered by pushing a release branch, use the default toolchain and version
compiler_toolchain="intel-classic"
compiler_version="2021.6"
echo "using default compiler toolchain $compiler_toolchain version $compiler_version"
else
# otherwise exit with an error
echo "error: this workflow should not have triggered for event ${{ github.event_name }} on branch ${{ github.ref_name }}"
exit 1
fi
echo "compiler_toolchain=$compiler_toolchain" >> $GITHUB_OUTPUT
echo "compiler_version=$compiler_version" >> $GITHUB_OUTPUT
- name: Set version
id: set_version
run: |
# if version number was provided explicitly via workflow_dispatch, use it
if [[ ("${{ github.event_name }}" == "workflow_dispatch") && (-n "${{ inputs.version }}") ]]; then
ver="${{ inputs.version }}"
echo "using version number $ver from workflow_dispatch"
elif [[ ("${{ github.event_name }}" == "push") && ("${{ github.ref_name }}" != "master") ]]; then
# if release was triggered by pushing a release branch, parse version number from branch name (sans leading 'v')
ref="${{ github.ref_name }}"
ver="${ref#"v"}"
echo "parsed version number $ver from branch name $ref"
else
# otherwise exit with an error
echo "error: version number not provided explicitly (via workflow_dispatch input) or implicitly (via branch name)"
exit 1
fi
echo "version=$ver" >> $GITHUB_OUTPUT
- name: Set patch
id: set_patch
run: |
# if patch was provided explicitly via workflow_dispatch, use it
if [[ ("${{ github.event_name }}" == "workflow_dispatch") && (-n "${{ inputs.patch }}") ]]; then
patch="${{ inputs.patch }}"
echo "using patch setting $patch from workflow_dispatch"
elif [[ ("${{ github.event_name }}" == "push") && ("${{ github.ref_name }}" != "master") ]]; then
# if release was triggered by pushing a release branch, check the version against the latest
# tag on master to determine if this is a patch release
latest_tag=$(git ls-remote --tags origin "6.*" | awk -F/ '{print $3}' | sort -V | tail -n1)
echo "latest version on master is $latest_tag"
IFS='.' read -r -a latest_parts <<< "$latest_tag"
IFS='.' read -r -a new_parts <<< "${{ steps.set_version.outputs.version }}"
if [[ ${#latest_parts[@]} -ne 3 || ${#new_parts[@]} -ne 3 ]]; then
echo "error: version number is not in major.minor.patch format"
exit 1
fi
if [[ ${latest_parts[0]} -ne ${new_parts[0]} || ${latest_parts[1]} -ne ${new_parts[1]} ]]; then
patch="false"
echo "major or minor version has changed, not a patch release"
elif [[ ${latest_parts[2]} -lt ${new_parts[2]} ]]; then
patch="true"
echo "patch version has changed, this is a patch release"
fi
else
# otherwise exit with an error
echo "error: this workflow should not have triggered for event ${{ github.event_name }} on branch ${{ github.ref_name }}"
exit 1
fi
echo "patch=$patch" >> $GITHUB_OUTPUT
- name: Set date
id: set_date
run: |
# one date for all jobs, so timestamps and the release history agree
echo "date=$(date -u +%F)" >> $GITHUB_OUTPUT
- name: Check release history
env:
BRANCH: ${{ steps.set_branch.outputs.branch }}
VERSION: ${{ steps.set_version.outputs.version }}
DOI: ${{ inputs.doi }}
run: |
# The release history in the release notes gets a row for the release during the build.
# It reuses the DOI of the previous release with the same major and minor version, so
# patch releases need no DOI, but a new minor release needs one: either from the doi
# input, or from a row already on the release branch. Fail now instead of in the build
# if there isn't one. Release candidates get no row.
git fetch --depth=1 origin "$BRANCH"
git show FETCH_HEAD:doc/ReleaseNotes/ReleaseNotes.tex > "$RUNNER_TEMP/ReleaseNotes.tex"
args=(-v "$VERSION" --check --notes "$RUNNER_TEMP/ReleaseNotes.tex")
if [[ -n "$DOI" ]]; then
args+=(--doi "$DOI")
fi
if ! python3 doc/ReleaseNotes/release_history.py "${args[@]}"; then
echo "Start the release with workflow_dispatch and provide the doi input, or add a row"
echo "for $VERSION to the release history in doc/ReleaseNotes/ReleaseNotes.tex on $BRANCH."
exit 1
fi
make_dist:
name: Make distribution
uses: MODFLOW-ORG/modflow6/.github/workflows/release.yml@develop
needs: set_options
with:
# If the workflow is manually triggered, the maintainer must manually set approve=true to approve a release.
# If triggered by pushing a release branch, the release is approved if the branch name doesn't contain "rc".
compiler_toolchain: ${{ needs.set_options.outputs.compiler_toolchain }}
compiler_version: ${{ needs.set_options.outputs.compiler_version }}
branch: ${{ needs.set_options.outputs.branch }}
# If the workflow is manually triggered, the maintainer must manually set releasemode to true, otherwise the default is false.
# If triggered by pushing a release branch, the release is developmode if the branch name contains "rc", otherwise releasemode.
releasemode: ${{ (github.event_name == 'workflow_dispatch' && inputs.releasemode == true) || github.event_name != 'workflow_dispatch' }}
# If the workflow is manually triggered, the maintainer must manually set run_tests to false, otherwise the default is true.
# If triggered by pushing a release branch, tests are enabled.
run_tests: ${{ (github.event_name == 'workflow_dispatch' && inputs.run_tests == true) || github.event_name != 'workflow_dispatch' }}
version: ${{ needs.set_options.outputs.version }}
patch: ${{ (github.event_name == 'workflow_dispatch' && inputs.patch == true) || (github.event_name != 'workflow_dispatch' && needs.set_options.outputs.patch == 'true') }}
# If triggered by pushing a release branch there is no input. A patch release reuses the previous DOI,
# and for a new minor release the release history row must already be on the branch.
doi: ${{ inputs.doi }}
# the same date for all jobs, so timestamps and the release history agree
date: ${{ needs.set_options.outputs.date }}
pr:
name: Draft release PR
if: ${{ github.ref_name != 'master' && ((github.event_name == 'workflow_dispatch' && inputs.releasemode == true) || (github.event_name != 'workflow_dispatch' && !contains(github.ref_name, 'rc'))) }}
needs:
- set_options
- make_dist
runs-on: ubuntu-22.04
permissions:
contents: write
pull-requests: write
defaults:
run:
shell: bash -l {0}
steps:
- name: Checkout modflow6
uses: actions/checkout@v7
with:
repository: ${{ github.repository_owner }}/modflow6
ref: ${{ github.ref }}
- name: Setup Micromamba
uses: mamba-org/setup-micromamba@v3
with:
environment-file: environment.yml
cache-downloads: true
cache-environment: true
- name: Update version
working-directory: distribution
env:
# empty if workflow was triggered by pushing a release branch
DOI: ${{ inputs.doi }}
DATE: ${{ needs.set_options.outputs.date }}
run: |
# update version files
ver="${{ needs.set_options.outputs.version }}"
args=(-v "$ver" --date "$DATE")
# approve will be empty if workflow was triggered by pushing a release branch
# todo: pull approve into set_options job/output?
if [[ ("${{ inputs.releasemode }}" == "true") || ("${{ inputs.releasemode }}" == "") ]]; then
args+=(--releasemode)
fi
python update_version.py "${args[@]}"
# add the release to the release history, using the DOI if provided
args=(-v "$ver" --date "$DATE")
if [[ -n "$DOI" ]]; then
args+=(--doi "$DOI")
fi
python ../doc/ReleaseNotes/release_history.py "${args[@]}"
# lint version.f90
fprettify -c ../.fprettify.yaml ../src/Utilities/version.f90
# commit and push
git config core.sharedRepository true
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
git add -A
git commit -m "ci(release): update version to $ver"
git push origin "${{ github.ref }}"
- name: Create pull request
env:
GITHUB_TOKEN: ${{ github.token }}
run: |
ver="${{ needs.set_options.outputs.version }}"
body='
# MODFLOW '$ver' release
The release can be approved by merging this PR into `master`. Merging rather than squashing is necessary to preserve the commit history.
When this PR is merged, a final job will be triggered to draft a tagged GitHub release, then upload assets (OS distributions and release notes).
'
gh pr create -B "master" -H "${{ github.ref }}" --title "Release $ver" --draft --body "$body"
release:
name: Draft release
# runs only after release PR is merged to master
if: github.event_name == 'push' && github.ref_name == 'master'
runs-on: ubuntu-22.04
defaults:
run:
shell: bash -l {0}
steps:
- name: Checkout modflow6
uses: actions/checkout@v7
with:
repository: ${{ github.repository_owner }}/modflow6
path: modflow6
- name: Setup Micromamba
uses: mamba-org/setup-micromamba@v3
with:
environment-file: modflow6/environment.yml
cache-downloads: true
cache-environment: true
- name: Download artifacts
uses: dawidd6/action-download-artifact@v25
- name: Draft release
working-directory: modflow6
env:
GITHUB_TOKEN: ${{ github.token }}
run: |
# create draft release
version=$(python distribution/update_version.py -g)
title="MODFLOW $version"
citation=$(python distribution/update_version.py -c)
notes='
This is the approved USGS MODFLOW '$version' release.
'$citation'
Visit the USGS "MODFLOW and Related Programs" site for information on MODFLOW 6 and related software: https://doi.org/10.5066/F76Q1VQV
'
gh release create "$version" ../mf*/mf*.zip ../release_notes/release.pdf --target master --title "$title" --notes "$notes" --draft --latest
reset:
name: Reset develop
# runs after a release is published. opens a PR to merge master back
# into develop with the version string updated for the next cycle
if: github.event_name == 'release'
runs-on: ubuntu-22.04
permissions:
contents: write
pull-requests: write
defaults:
run:
shell: bash -l {0}
steps:
- name: Checkout modflow6
uses: actions/checkout@v7
with:
repository: ${{ github.repository_owner }}/modflow6
ref: master
fetch-depth: 0
- name: Setup Micromamba
uses: mamba-org/setup-micromamba@v3
with:
environment-file: environment.yml
cache-downloads: true
cache-environment: true
- name: Archive release notes
working-directory: doc/ReleaseNotes
run: |
# the released version, since we branched from master (and this runs
# before the version bump below)
ver=$(cat ../../version.txt)
# a non-zero patch number means a patch release: archive and clear
# only the fix and example items, the rest carry to the next minor release
patch=""
[ "$(echo "$ver" | cut -d. -f3)" != "0" ] && patch="--patch"
# archive this version's notes to previous/v$ver.tex, register them
# in appendixA.tex, and clear the archived items from develop.toml
python reset_releasenotes.py $patch
- name: Update version and open PR
working-directory: distribution
env:
GITHUB_TOKEN: ${{ github.token }}
run: |
# the released version, since we branched from master
ver=$(cat ../version.txt)
branch="post-release-$ver-reset"
# bump minor and add '.dev0' suffix
next=$(python update_version.py --post-release)
# lint the generated source
fprettify -c ../.fprettify.yaml ../src/Utilities/version.f90
# commit and push
git config core.sharedRepository true
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
git switch -c "$branch"
git add -A
git commit -m "ci(release): update version to $next, archive release notes"
git push origin "$branch"
# create PR
body='
# Reset `develop` after release '$ver'
Merge (do not squash) this pull request to bring `master` back into `develop`,
set the development version to `'$next'`, and archive the `'$ver'` release notes.
'
gh pr create -B "develop" -H "$branch" --title "Post release $ver reset" --body "$body"