@@ -66,8 +66,8 @@ kinds of builds (sets of jobs).
66
66
### Pull Request builds
67
67
68
68
After each push to a pull request, a set of ` pr ` jobs are executed. Currently,
69
- these execute the ` x86_64-gnu-llvm-X ` , ` x86_64-gnu-tools ` , ` mingw -check-1` , ` mingw -check-2`
70
- and ` mingw-check- tidy` jobs, all running on Linux. These execute a relatively short
69
+ these execute the ` x86_64-gnu-llvm-X ` , ` x86_64-gnu-tools ` , ` pr -check-1` , ` pr -check-2`
70
+ and ` tidy ` jobs, all running on Linux. These execute a relatively short
71
71
(~ 40 minutes) and lightweight test suite that should catch common issues. More
72
72
specifically, they run a set of lints, they try to perform a cross-compile check
73
73
build to Windows mingw (without producing any artifacts) and they test the
@@ -148,6 +148,13 @@ for example `*msvc*` or `*-alt`. You can start at most 20 jobs in a single try b
148
148
glob patterns, you might want to wrap them in backticks (`` ` `` ) to avoid GitHub rendering
149
149
the pattern as Markdown.
150
150
151
+ The job pattern needs to match one or more jobs defined in the ` auto ` or ` optional ` sections
152
+ of [ ` jobs.yml ` ] :
153
+
154
+ - ` auto ` jobs are executed before a commit is merged into the ` master ` branch.
155
+ - ` optional ` jobs are executed only when explicitly requested via a try build.
156
+ They are typically used for tier 2 and tier 3 targets.
157
+
151
158
> ** Using ` try-job ` PR description directives**
152
159
>
153
160
> 1 . Identify which set of try-jobs you would like to exercise. You can
0 commit comments