-
Notifications
You must be signed in to change notification settings - Fork 0
/
test-and-release.yml
63 lines (53 loc) · 3.3 KB
/
test-and-release.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
52
53
54
55
56
57
58
59
60
61
62
63
name: Run tests and update release
on:
# Only one trigger is necessary, keep only the ones you need. Default branch is set by default, change it according to your needs.
# Find more information here: # https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows
push:
branches: [ $default-branch ]
pull_request:
branches: [ $default-branch ]
schedule:
- cron: '0 0 * * *'
jobs:
run-tests-and-update-release:
name: Run tests and update release
uses: moosetechnology/.github/.github/workflows/test-and-release.yml@main
# Optional inputs: un-comment the lines below. See documentation in the next commented paragraph.
# with:
# pharo-versions: [ Pharo64-stable ]
# image-name: ""
# pre-upload-script: ""
# release-tag: ""
# run-coverage: true
############ INPUTS DOCUMENTATION ############
# pharo-version:
# An array of strings corresponding to a Pharo or Moose image.
# Default is the Pharo versions compatible with the latest Moose version.
# Alternatively, you can:
# - set the value of this option with valid Pharo or Moose versions (always an array, even if you set only 1 image). See available images here: https://github.com/hpi-swa/smalltalkCI?tab=readme-ov-file#images
# - assign a Moose version to your branch using repository variables. See https://github.com/moosetechnology/.github?tab=readme-ov-file#use-different-values-for-specfic-branches
# The default Pharo version will then be the available Pharo versions corresponding to this Moose version.
# image-name:
# A string.
# If create-artifact is set to true, this will be the beginning of the name of the artifact and the image in it.
# The full name of each artifact will be <imagename>-<pharo-version>. This way you get an artifact per pharo version used.
# Default value: <RepositoryName-branchName>
# Alternatively, you can:
# - set the value of this option to a name valid for all branches targeted by your workflow
# - assign an image name to your branch using repository variables. See https://github.com/moosetechnology/.github?tab=readme-ov-file#use-different-values-for-specfic-branches
# pre-upload-script:
# A string that can be executed in Pharo.
# If create-artifact is set to true, this will be executed in the image after the tests are run and before uploading the artifact.
# It is mostly used when you need to register information from the workflow run. For example, store commit ID.
# If you do not need workflow information, you can instead use smalltalkCI custom scripts: https://github.com/hpi-swa/smalltalkCI?tab=readme-ov-file#custom-scripts
# Default value: ""
# release-tag:
# A string corresponding to tag of the release you want to update.
# Default value: 'generated-assets'
# Alternatively, you can
# - set the value of this option to a tag valid for all branches targeted by your workflow
# - assign a release tag to your branch using repository variables. See https://github.com/moosetechnology/.github?tab=readme-ov-file#use-different-values-for-specfic-branches
# run-coverage:
# Compute coverage using Coveralls.
# See https://github.com/hpi-swa/smalltalkCI/blob/master/docs/COVERAGE.md for more documentation.
# Be sure to run on packages or classes in the repository (not loaded via dependency)