forked from mamba-org/provision-with-micromamba
-
Notifications
You must be signed in to change notification settings - Fork 0
/
action.yml
62 lines (61 loc) · 2.3 KB
/
action.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
name: "provision-with-micromamba"
description: "provision a CI instance using micromamba"
branding:
icon: "chevrons-right"
color: "green"
inputs:
environment-file:
description: >-
The environment.yml or .lock file for the conda environment.
If 'false', no enviroment will be created (only Micromamba will be installed).
required: true
default: environment.yml
environment-name:
description: >-
The name of the conda environment (defaults to name from the environment.yml file).
Required if 'environment-file' is a '.lock' file or 'false'.
required: false
micromamba-version:
description: >-
Version of micromamba to use, eg. '0.20' (default 'latest').
required: false
default: "latest"
extra-specs:
description: >-
Additional specifications (packages) to install.
Pretty useful when using matrix builds to pin versions of a test/run dependency.
For multiple packages, use multiline syntax (see examples).
required: false
default: ""
cache-downloads:
description: >-
If 'true', cache downloaded packages across calls to the provision-with-micromamba action.
Cache invalidation can be controlled using the 'cache-downloads-key' option.
default: false
cache-downloads-key:
description: >-
Optional custom download cache key used with 'cache-downloads: true'.
The default download cache key will invalidate the cache once per day.
required: false
cache-env:
description: >-
If 'true', cache installed environments across calls to the provision-with-micromamba action.
Cache invalidation can be controlled using the 'cache-env-key' option.
default: false
cache-env-key:
description: >-
Optional custom environment cache key used with 'cache-env: true'.
The default environment cache key will invalidate the cache whenever the contents of the
'environment-file' or 'extra-specs' change, plus once per day.
required: false
cache-env-always-update:
description: >-
(Not implemented)
If 'true', run 'micromamba update' even if the environment was restored from cache
to make sure your environment is always up-to-date.
default: false
runs:
using: "node16"
main: "dist/main/index.js"
post: "dist/post/index.js"
post-if: success()