You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lib/package/concurrency.ts
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,12 @@ import type { Expression } from "./expression";
3
3
exporttypeConcurrency=
4
4
|string
5
5
|{
6
+
/**
7
+
* When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled.
8
+
*/
6
9
group: string;
10
+
/**
11
+
* To cancel any currently running job or workflow in the same concurrency group, specify true.
* A strategy creates a build matrix for your jobs.
41
+
* You can define different variations of an environment to run each job in.
42
+
*/
25
43
strategy?: Strategy;
44
+
/**
45
+
* Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time.
46
+
* A concurrency group can be any string or expression.
47
+
* The expression can use any context except for the secrets context.
48
+
* You can also specify concurrency at the workflow level.
49
+
* When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending.
50
+
* Any previously pending job or workflow in the concurrency group will be canceled.
51
+
* To also cancel any currently running job or workflow in the same concurrency group, specify `cancelInProgress: true`.
52
+
*/
26
53
concurrency?: Concurrency;
27
54
};
28
55
29
56
exporttypeNormalJobConfig=JobConfigBase&{
57
+
/**
58
+
* The type of machine to run the job on.
59
+
* The machine can be either a GitHub-hosted runner, or a self-hosted runner.
60
+
*/
30
61
runsOn: RunsOn;
62
+
/**
63
+
* The environment that the job references.
64
+
*/
31
65
environment?: Environment;
66
+
/**
67
+
* A map of outputs for a job.
68
+
* Job outputs are available to all downstream jobs that depend on this job.
69
+
*/
32
70
outputs?: Record<string,string>;
71
+
/**
72
+
* A map of environment variables that are available to all steps in the job.
73
+
*/
33
74
env?: Env;
75
+
/**
76
+
* A map of default settings that will apply to all steps in the job.
77
+
*/
34
78
defaults?: Defaults;
79
+
/**
80
+
* The maximum number of minutes to let a workflow run before GitHub automatically cancels it.
81
+
* @default 360
82
+
*/
35
83
timeoutMinutes?: number|Expression;
84
+
/**
85
+
* Prevents a workflow run from failing when a job fails.
86
+
* Set to true to allow a workflow run to pass when this job fails.
87
+
*/
36
88
continueOnError?: boolean|Expression;
89
+
/**
90
+
* A container to run any steps in a job that don't already specify a container.
91
+
* If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts.
92
+
* If you do not set a container, all steps will run directly on the host specified by runs-on unless a step refers to an action configured to run in a container.
93
+
*/
37
94
container?: Container;
95
+
/**
96
+
* Additional containers to host services for a job in a workflow.
97
+
* These are useful for creating databases or cache services like redis.
98
+
* The runner on the virtual machine will automatically create a network and manage the life cycle of the service containers.
99
+
* When you use a service container for a job or your step uses container actions, you don't need to set port information to access the service.
100
+
* Docker automatically exposes all ports between containers on the same network.
101
+
* When both the job and the action run in a container, you can directly reference the container by its hostname.
102
+
* The hostname is automatically mapped to the service name.
103
+
* When a step does not use a container action, you must access the service using localhost and bind the ports.
Copy file name to clipboardExpand all lines: lib/package/matrix.ts
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,15 @@
1
1
importtype{Expression}from"./expression";
2
2
3
+
/**
4
+
* A build matrix is a set of different configurations of the virtual environment.
5
+
* For example you might run a job against more than one supported version of a language, operating system, or tool.
6
+
* Each configuration is a copy of the job that runs and reports a status.
7
+
* You can specify a matrix by supplying an array for the configuration options.
8
+
* For example, if the GitHub virtual environment supports Node.js versions 6, 8, and 10 you could specify an array of those versions in the matrix.
9
+
* When you define a matrix of operating systems, you must set the required runs-on keyword to the operating system of the current job, rather than hard-coding the operating system name.
10
+
* To access the operating system name, you can use the matrix.os context parameter to set runs-on.
0 commit comments