# rustc version rustc 1.98.0-nightly (23a3312d9 2026-05-23)
# docs.rs version docsrs 0.0.0 (f16e33f3e6ac9fc9e4413728c5dd1b2ba1c6b799 2026-05-23 )
# build log [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-w" "/opt/rustwide/workdir" "--user" "1001:1001" "cf07855aea73038b33ac4ff286c1a6ed42400ced23a15a117e23bc6033a17959" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260523-1.98.0-nightly-23a3312d9\", \"--static-root-path\", \"/-/rustdoc.static/\", \"--cap-lints\", \"warn\", \"--extern-html-root-takes-precedence\"]" "--offline" "-Zunstable-options" "--config=doc.extern-map.registries.crates-io=\"https://docs.rs/{pkg_name}/{version}/x86_64-unknown-linux-gnu\"" "-Zrustdoc-scrape-examples" "-j6" "--target" "x86_64-unknown-linux-gnu", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting rusoto_codebuild v0.48.0 (/opt/rustwide/workdir) [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:216:212 [INFO] [stderr] | [INFO] [stderr] 216 | ...e>FAULT</code>: The build faulted.</p> </li> <li> <p> <code>IN<em>PROGRESS</code>: The build is still in progress.</p> </li> <li... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(rustdoc::invalid_html_tags)]` on by default [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 216 | /// <p><p>The current status of the build. Valid values include:</p> <ul> <li> <p> <code>FAILED</code>: The build failed.</p> </li> <li> <p> <code>FAULT</code>: The build faulted.</p> </li> <li> <p> <code>`IN<em>`PROGRESS</code>: The build is still in progress.</p> </li> <li> <p> <code>STOPPED</code>: The build stopped.</p> </li> <li> <p> <code>SUCCEEDED</code>: The build succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build timed out.</p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:216:419 [INFO] [stderr] | [INFO] [stderr] 216 | ...D</code>: The build succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build timed out.</p> </li> </ul></p> [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:502:213 [INFO] [stderr] | [INFO] [stderr] 502 | ...t>FAULT</dt> <dd> <p>The build phase faulted.</p> </dd> <dt>IN<em>PROGRESS</dt> <dd> <p>The build phase is still in progress.</p... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 502 | /// <p><p>The current status of the batch build phase. Valid values include:</p> <dl> <dt>FAILED</dt> <dd> <p>The build phase failed.</p> </dd> <dt>FAULT</dt> <dd> <p>The build phase faulted.</p> </dd> <dt>`IN<em>`PROGRESS</dt> <dd> <p>The build phase is still in progress.</p> </dd> <dt>QUEUED</dt> <dd> <p>The build has been submitted and is queued behind other submitted builds.</p> </dd> <dt>STOPPED</dt> <dd> <p>The build phase stopped.</p> </dd> <dt>SUCCEEDED</dt> <dd> <p>The build phase succeeded.</p> </dd> <dt>TIMED</em>OUT</dt> <dd> <p>The build phase timed out.</p> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:502:528 [INFO] [stderr] | [INFO] [stderr] 502 | ...D</dt> <dd> <p>The build phase succeeded.</p> </dd> <dt>TIMED</em>OUT</dt> <dd> <p>The build phase timed out.</p> </dd> </dl></p> [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:506:92 [INFO] [stderr] | [INFO] [stderr] 506 | /// <p><p>The name of the batch build phase. Valid values include:</p> <dl> <dt>COMBINE<em>ARTIFACTS</dt> <dd> <p>Build output ... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 506 | /// <p><p>The name of the batch build phase. Valid values include:</p> <dl> <dt>`COMBINE<em>`ARTIFACTS</dt> <dd> <p>Build output artifacts are being combined and uploaded to the output location.</p> </dd> <dt>DOWNLOAD</em>BATCHSPEC</dt> <dd> <p>The batch build specification is being downloaded.</p> </dd> <dt>FAILED</dt> <dd> <p>One or more of the builds failed.</p> </dd> <dt>IN_PROGRESS</dt> <dd> <p>The batch build is in progress.</p> </dd> <dt>STOPPED</dt> <dd> <p>The batch build was stopped.</p> </dd> <dt>SUBMITTED</dt> <dd> <p>The btach build has been submitted.</p> </dd> <dt>SUCCEEDED</dt> <dd> <p>The batch build succeeded.</p> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:506:220 [INFO] [stderr] | [INFO] [stderr] 506 | ...d and uploaded to the output location.</p> </dd> <dt>DOWNLOAD</em>BATCHSPEC</dt> <dd> <p>The batch build specification is being ... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:572:207 [INFO] [stderr] | [INFO] [stderr] 572 | ...t>FAULT</dt> <dd> <p>The build phase faulted.</p> </dd> <dt>IN<em>PROGRESS</dt> <dd> <p>The build phase is still in progress.</p... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 572 | /// <p><p>The current status of the build phase. Valid values include:</p> <dl> <dt>FAILED</dt> <dd> <p>The build phase failed.</p> </dd> <dt>FAULT</dt> <dd> <p>The build phase faulted.</p> </dd> <dt>`IN<em>`PROGRESS</dt> <dd> <p>The build phase is still in progress.</p> </dd> <dt>QUEUED</dt> <dd> <p>The build has been submitted and is queued behind other submitted builds.</p> </dd> <dt>STOPPED</dt> <dd> <p>The build phase stopped.</p> </dd> <dt>SUCCEEDED</dt> <dd> <p>The build phase succeeded.</p> </dd> <dt>TIMED</em>OUT</dt> <dd> <p>The build phase timed out.</p> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:572:522 [INFO] [stderr] | [INFO] [stderr] 572 | ...D</dt> <dd> <p>The build phase succeeded.</p> </dd> <dt>TIMED</em>OUT</dt> <dd> <p>The build phase timed out.</p> </dd> </dl></p> [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:576:269 [INFO] [stderr] | [INFO] [stderr] 576 | ...he build has been completed.</p> </li> <li> <p> <code>DOWNLOAD<em>SOURCE</code>: Source code is being downloaded in this build p... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 576 | /// <p><p>The name of the build phase. Valid values include:</p> <ul> <li> <p> <code>BUILD</code>: Core build activities typically occur in this build phase.</p> </li> <li> <p> <code>COMPLETED</code>: The build has been completed.</p> </li> <li> <p> <code>`DOWNLOAD<em>`SOURCE</code>: Source code is being downloaded in this build phase.</p> </li> <li> <p> <code>FINALIZING</code>: The build process is completing in this build phase.</p> </li> <li> <p> <code>INSTALL</code>: Installation activities typically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PRE<em>BUILD</code>: Pre-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PROVISIONING</code>: The build environment is being set up.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>SUBMITTED</code>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to the output location.</p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:576:569 [INFO] [stderr] | [INFO] [stderr] 576 | ...ally occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this bu... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:576:675 [INFO] [stderr] | [INFO] [stderr] 576 | ...ically occur in this build phase.</p> </li> <li> <p> <code>PRE<em>BUILD</code>: Pre-build activities typically occur in this bui... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 576 | /// <p><p>The name of the build phase. Valid values include:</p> <ul> <li> <p> <code>BUILD</code>: Core build activities typically occur in this build phase.</p> </li> <li> <p> <code>COMPLETED</code>: The build has been completed.</p> </li> <li> <p> <code>DOWNLOAD<em>SOURCE</code>: Source code is being downloaded in this build phase.</p> </li> <li> <p> <code>FINALIZING</code>: The build process is completing in this build phase.</p> </li> <li> <p> <code>INSTALL</code>: Installation activities typically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build phase.</p> </li> <li> <p> <code>`PRE<em>`BUILD</code>: Pre-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PROVISIONING</code>: The build environment is being set up.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>SUBMITTED</code>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to the output location.</p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:576:1054 [INFO] [stderr] | [INFO] [stderr] 576 | ...The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:607:177 [INFO] [stderr] | [INFO] [stderr] 607 | ...t>FAULT</dt> <dd> <p>The build group faulted.</p> </dd> <dt>IN<em>PROGRESS</dt> <dd> <p>The build group is still in progress.</p... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 607 | /// <p><p>The status of the build group.</p> <dl> <dt>FAILED</dt> <dd> <p>The build group failed.</p> </dd> <dt>FAULT</dt> <dd> <p>The build group faulted.</p> </dd> <dt>`IN<em>`PROGRESS</dt> <dd> <p>The build group is still in progress.</p> </dd> <dt>STOPPED</dt> <dd> <p>The build group stopped.</p> </dd> <dt>SUCCEEDED</dt> <dd> <p>The build group succeeded.</p> </dd> <dt>TIMED</em>OUT</dt> <dd> <p>The build group timed out.</p> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:607:384 [INFO] [stderr] | [INFO] [stderr] 607 | ...D</dt> <dd> <p>The build group succeeded.</p> </dd> <dt>TIMED</em>OUT</dt> <dd> <p>The build group timed out.</p> </dd> </dl></p> [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1008:91 [INFO] [stderr] | [INFO] [stderr] 1008 | /// <p><p>Specifies how the results are sorted. Possible values are:</p> <dl> <dt>FILE<em>PATH</dt> <dd> <p>The results are so... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1008 | /// <p><p>Specifies how the results are sorted. Possible values are:</p> <dl> <dt>`FILE<em>`PATH</dt> <dd> <p>The results are sorted by file path.</p> </dd> <dt>LINE</em>COVERAGE_PERCENTAGE</dt> <dd> <p>The results are sorted by the percentage of lines that are covered.</p> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1008:168 [INFO] [stderr] | [INFO] [stderr] 1008 | ...d> <p>The results are sorted by file path.</p> </dd> <dt>LINE</em>COVERAGE_PERCENTAGE</dt> <dd> <p>The results are sorted by th... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1116:104 [INFO] [stderr] | [INFO] [stderr] 1116 | /// <p><p>The type of environment variable. Valid values include:</p> <ul> <li> <p> <code>PARAMETER<em>STORE</code>: An enviro... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1116 | /// <p><p>The type of environment variable. Valid values include:</p> <ul> <li> <p> <code>`PARAMETER<em>`STORE</code>: An environment variable stored in Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see <a href="https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.parameter-store">env/parameter-store</a> in the <i>CodeBuild User Guide</i>.</p> </li> <li> <p> <code>PLAINTEXT</code>: An environment variable in plain text format. This is the default value.</p> </li> <li> <p> <code>SECRETS</em>MANAGER</code>: An environment variable stored in Secrets Manager. To learn how to specify a secrets manager environment variable, see <a href="https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.secrets-manager">env/secrets-manager</a> in the <i>CodeBuild User Guide</i>.</p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1116:581 [INFO] [stderr] | [INFO] [stderr] 1116 | .... This is the default value.</p> </li> <li> <p> <code>SECRETS</em>MANAGER</code>: An environment variable stored in Secrets Man... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1120:489 [INFO] [stderr] | [INFO] [stderr] 1120 | ...mmend you use an environment variable of type <code>PARAMETER<em>STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </impor... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1120 | /// <p><p>The value of the environment variable.</p> <important> <p>We strongly discourage the use of <code>PLAINTEXT</code> environment variables to store sensitive values, especially Amazon Web Services secret key IDs and secret access keys. <code>PLAINTEXT</code> environment variables can be displayed in plain text using the CodeBuild console and the AWS Command Line Interface (AWS CLI). For sensitive values, we recommend you use an environment variable of type <code>`PARAMETER<em>`STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </important></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1120:522 [INFO] [stderr] | [INFO] [stderr] 1120 | ...able of type <code>PARAMETER<em>STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </important></p> [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1125:648 [INFO] [stderr] | [INFO] [stderr] 1125 | ... the <code>install</code> phase and the end of the <code>post<em>build</code> phase. After the <code>post</em>build</code> phas... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1125 | /// <p><p>Contains information about an exported environment variable. </p> <p>Exported environment variables are used in conjunction with CodePipeline to export environment variables from the current build stage to subsequent stages in the pipeline. For more information, see <a href="https://docs.aws.amazon.com/codepipeline/latest/userguide/actions-variables.html">Working with variables</a> in the <i>CodePipeline User Guide</i>.</p> <note> <p> During a build, the value of a variable is available starting with the <code>install</code> phase. It can be updated between the start of the <code>install</code> phase and the end of the <code>`post<em>`build</code> phase. After the <code>post</em>build</code> phase ends, the value of exported variables cannot change.</p> </note></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1125:692 [INFO] [stderr] | [INFO] [stderr] 1125 | ...of the <code>post<em>build</code> phase. After the <code>post</em>build</code> phase ends, the value of exported variables cann... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1149:237 [INFO] [stderr] | [INFO] [stderr] 1149 | ... test run times for the specified reports.</p> </dd> <dt>PASS<em>RATE</dt> <dd> <p>Accumulate the percentage of tests that pass... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1149 | /// <p><p>The test report value to accumulate. This must be one of the following values:</p> <dl> <dt>Test reports:</dt> <dd> <dl> <dt>DURATION</dt> <dd> <p>Accumulate the test run times for the specified reports.</p> </dd> <dt>`PASS<em>`RATE</dt> <dd> <p>Accumulate the percentage of tests that passed for the specified test reports.</p> </dd> <dt>TOTAL</dt> <dd> <p>Accumulate the total number of tests for the specified test reports.</p> </dd> </dl> </dd> </dl> <dl> <dt>Code coverage reports:</dt> <dd> <dl> <dt>BRANCH</em>COVERAGE</dt> <dd> <p>Accumulate the branch coverage percentages for the specified test reports.</p> </dd> <dt>BRANCHES<em>COVERED</dt> <dd> <p>Accumulate the branches covered values for the specified test reports.</p> </dd> <dt>BRANCHES</em>MISSED</dt> <dd> <p>Accumulate the branches missed values for the specified test reports.</p> </dd> <dt>LINE<em>COVERAGE</dt> <dd> <p>Accumulate the line coverage percentages for the specified test reports.</p> </dd> <dt>LINES</em>COVERED</dt> <dd> <p>Accumulate the lines covered values for the specified test reports.</p> </dd> <dt>LINES_MISSED</dt> <dd> <p>Accumulate the lines not covered values for the specified test reports.</p> </dd> </dl> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1149:525 [INFO] [stderr] | [INFO] [stderr] 1149 | ...dl> <dl> <dt>Code coverage reports:</dt> <dd> <dl> <dt>BRANCH</em>COVERAGE</dt> <dd> <p>Accumulate the branch coverage percenta... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1149:649 [INFO] [stderr] | [INFO] [stderr] 1149 | ...ntages for the specified test reports.</p> </dd> <dt>BRANCHES<em>COVERED</dt> <dd> <p>Accumulate the branches covered values fo... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1149 | /// <p><p>The test report value to accumulate. This must be one of the following values:</p> <dl> <dt>Test reports:</dt> <dd> <dl> <dt>DURATION</dt> <dd> <p>Accumulate the test run times for the specified reports.</p> </dd> <dt>PASS<em>RATE</dt> <dd> <p>Accumulate the percentage of tests that passed for the specified test reports.</p> </dd> <dt>TOTAL</dt> <dd> <p>Accumulate the total number of tests for the specified test reports.</p> </dd> </dl> </dd> </dl> <dl> <dt>Code coverage reports:</dt> <dd> <dl> <dt>BRANCH</em>COVERAGE</dt> <dd> <p>Accumulate the branch coverage percentages for the specified test reports.</p> </dd> <dt>`BRANCHES<em>`COVERED</dt> <dd> <p>Accumulate the branches covered values for the specified test reports.</p> </dd> <dt>BRANCHES</em>MISSED</dt> <dd> <p>Accumulate the branches missed values for the specified test reports.</p> </dd> <dt>LINE<em>COVERAGE</dt> <dd> <p>Accumulate the line coverage percentages for the specified test reports.</p> </dd> <dt>LINES</em>COVERED</dt> <dd> <p>Accumulate the lines covered values for the specified test reports.</p> </dd> <dt>LINES_MISSED</dt> <dd> <p>Accumulate the lines not covered values for the specified test reports.</p> </dd> </dl> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1149:767 [INFO] [stderr] | [INFO] [stderr] 1149 | ...values for the specified test reports.</p> </dd> <dt>BRANCHES</em>MISSED</dt> <dd> <p>Accumulate the branches missed values for... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1149:880 [INFO] [stderr] | [INFO] [stderr] 1149 | ...sed values for the specified test reports.</p> </dd> <dt>LINE<em>COVERAGE</dt> <dd> <p>Accumulate the line coverage percentages... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1149 | /// <p><p>The test report value to accumulate. This must be one of the following values:</p> <dl> <dt>Test reports:</dt> <dd> <dl> <dt>DURATION</dt> <dd> <p>Accumulate the test run times for the specified reports.</p> </dd> <dt>PASS<em>RATE</dt> <dd> <p>Accumulate the percentage of tests that passed for the specified test reports.</p> </dd> <dt>TOTAL</dt> <dd> <p>Accumulate the total number of tests for the specified test reports.</p> </dd> </dl> </dd> </dl> <dl> <dt>Code coverage reports:</dt> <dd> <dl> <dt>BRANCH</em>COVERAGE</dt> <dd> <p>Accumulate the branch coverage percentages for the specified test reports.</p> </dd> <dt>BRANCHES<em>COVERED</dt> <dd> <p>Accumulate the branches covered values for the specified test reports.</p> </dd> <dt>BRANCHES</em>MISSED</dt> <dd> <p>Accumulate the branches missed values for the specified test reports.</p> </dd> <dt>`LINE<em>`COVERAGE</dt> <dd> <p>Accumulate the line coverage percentages for the specified test reports.</p> </dd> <dt>LINES</em>COVERED</dt> <dd> <p>Accumulate the lines covered values for the specified test reports.</p> </dd> <dt>LINES_MISSED</dt> <dd> <p>Accumulate the lines not covered values for the specified test reports.</p> </dd> </dl> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1149:998 [INFO] [stderr] | [INFO] [stderr] 1149 | ...rcentages for the specified test reports.</p> </dd> <dt>LINES</em>COVERED</dt> <dd> <p>Accumulate the lines covered values for ... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1416:124 [INFO] [stderr] | [INFO] [stderr] 1416 | /// <p><p> The criterion to be used to list build report groups. Valid values include: </p> <ul> <li> <p> <code>CREATED<em>TIM... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1416 | /// <p><p> The criterion to be used to list build report groups. Valid values include: </p> <ul> <li> <p> <code>`CREATED<em>`TIME</code>: List based on when each report group was created.</p> </li> <li> <p> <code>LAST</em>MODIFIED_TIME</code>: List based on when each report group was last changed.</p> </li> <li> <p> <code>NAME</code>: List based on each report group's name.</p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1416:220 [INFO] [stderr] | [INFO] [stderr] 1416 | ... each report group was created.</p> </li> <li> <p> <code>LAST</em>MODIFIED_TIME</code>: List based on when each report group wa... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1791:407 [INFO] [stderr] | [INFO] [stderr] 1791 | ...ld.</p> </li> <li> <p>If <code>type</code> is set to <code>NO<em>ARTIFACTS</code>, this value is ignored if specified, because ... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1791 | /// <p><p>Along with <code>path</code> and <code>namespaceType</code>, the pattern that CodeBuild uses to name and store the output artifact:</p> <ul> <li> <p>If <code>type</code> is set to <code>CODEPIPELINE</code>, CodePipeline ignores this value if specified. This is because CodePipeline manages its build output names instead of CodeBuild.</p> </li> <li> <p>If <code>type</code> is set to <code>`NO<em>`ARTIFACTS</code>, this value is ignored if specified, because no build output is produced.</p> </li> <li> <p>If <code>type</code> is set to <code>S3</code>, this is the name of the output artifact object. If you set the name to be a forward slash ("/"), the artifact is stored in the root of the output bucket.</p> </li> </ul> <p>For example:</p> <ul> <li> <p> If <code>path</code> is set to <code>MyArtifacts</code>, <code>namespaceType</code> is set to <code>BUILD</em>ID</code>, and <code>name</code> is set to <code>MyArtifact.zip</code>, then the output artifact is stored in <code>MyArtifacts/<build-ID>/MyArtifact.zip</code>. </p> </li> <li> <p> If <code>path</code> is empty, <code>namespaceType</code> is set to <code>NONE</code>, and <code>name</code> is set to "<code>/</code>", the output artifact is stored in the root of the output bucket. </p> </li> <li> <p> If <code>path</code> is set to <code>MyArtifacts</code>, <code>namespaceType</code> is set to <code>BUILD_ID</code>, and <code>name</code> is set to "<code>/</code>", the output artifact is stored in <code>MyArtifacts/<build-ID></code>. </p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1791:887 [INFO] [stderr] | [INFO] [stderr] 1791 | ...acts</code>, <code>namespaceType</code> is set to <code>BUILD</em>ID</code>, and <code>name</code> is set to <code>MyArtifact.z... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1858:699 [INFO] [stderr] | [INFO] [stderr] 1858 | ...e option is ignored. </p> </dd> <dt>LOCAL<em>DOCKER</em>LAYER<em>CACHE</dt> <dd> <p>Caches existing Docker layers. This mode is... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1858 | /// <p><p>An array of strings that specify the local cache modes. You can use one or more local cache modes at the same time. This is only used for <code>LOCAL</code> cache types.</p> <p>Possible values are:</p> <dl> <dt>LOCAL<em>SOURCE</em>CACHE</dt> <dd> <p>Caches Git metadata for primary and secondary sources. After the cache is created, subsequent builds pull only the change between commits. This mode is a good choice for projects with a clean working directory and a source that is a large Git repository. If you choose this option and your project does not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket), the option is ignored. </p> </dd> <dt>LOCAL<em>DOCKER</em>`LAYER<em>`CACHE</dt> <dd> <p>Caches existing Docker layers. This mode is a good choice for projects that build or pull large Docker images. It can prevent the performance issues caused by pulling large Docker images down from the network. </p> <note> <ul> <li> <p>You can use a Docker layer cache in the Linux environment only. </p> </li> <li> <p>The <code>privileged</code> flag must be set so that your project has the required Docker permissions. </p> </li> <li> <p>You should consider the security implications before you use a Docker layer cache. </p> </li> </ul> </note> </dd> <dt>LOCAL</em>CUSTOM_CACHE</dt> <dd> <p>Caches directories you specify in the buildspec file. This mode is a good choice if your build scenario is not suited to one of the other three local cache modes. If you use a custom cache: </p> <ul> <li> <p>Only directories can be specified for caching. You cannot specify individual files. </p> </li> <li> <p>Symlinks are used to reference cached directories. </p> </li> <li> <p>Cached directories are linked to your build before it downloads its project sources. Cached items are overridden if a source item has the same name. Directories are specified using cache paths in the buildspec file. </p> </li> </ul> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1858:1285 [INFO] [stderr] | [INFO] [stderr] 1858 | ... Docker layer cache. </p> </li> </ul> </note> </dd> <dt>LOCAL</em>CUSTOM_CACHE</dt> <dd> <p>Caches directories you specify in t... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:1965:561 [INFO] [stderr] | [INFO] [stderr] 1965 | ... Enterprise Cloud repository.</p> </li> <li> <p> <code>GITHUB<em>ENTERPRISE</code>: The source code is in a GitHub Enterprise S... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 1965 | /// <p><p>The type of repository that contains the source code to be built. Valid values include:</p> <ul> <li> <p> <code>BITBUCKET</code>: The source code is in a Bitbucket repository.</p> </li> <li> <p> <code>CODECOMMIT</code>: The source code is in an CodeCommit repository.</p> </li> <li> <p> <code>CODEPIPELINE</code>: The source code settings are specified in the source action of a pipeline in CodePipeline.</p> </li> <li> <p> <code>GITHUB</code>: The source code is in a GitHub or GitHub Enterprise Cloud repository.</p> </li> <li> <p> <code>`GITHUB<em>`ENTERPRISE</code>: The source code is in a GitHub Enterprise Server repository.</p> </li> <li> <p> <code>NO</em>SOURCE</code>: The project does not have input source code.</p> </li> <li> <p> <code>S3</code>: The source code is in an Amazon S3 bucket.</p> </li> </ul></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:1965:672 [INFO] [stderr] | [INFO] [stderr] 1965 | ...Hub Enterprise Server repository.</p> </li> <li> <p> <code>NO</em>SOURCE</code>: The project does not have input source code.</... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:148 [INFO] [stderr] | [INFO] [stderr] 2900 | ...VENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</cod... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 2900 | /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>`HEAD<em>`REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:174 [INFO] [stderr] | [INFO] [stderr] 2900 | ...m>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>M... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:201 [INFO] [stderr] | [INFO] [stderr] 2900 | ...ode>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <d... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 2900 | /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>`FILE<em>`PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:234 [INFO] [stderr] | [INFO] [stderr] 2900 | ...E</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:1159 [INFO] [stderr] | [INFO] [stderr] 2900 | ...regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the h... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 2900 | /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> `HEAD<em>`REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:1547 [INFO] [stderr] | [INFO] [stderr] 2900 | ...push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the ... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unclosed HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:1812 [INFO] [stderr] | [INFO] [stderr] 2900 | ...s with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path o... [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] help: try marking as source code [INFO] [stderr] | [INFO] [stderr] 2900 | /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> `FILE<em>`PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p> [INFO] [stderr] | + + [INFO] [stderr] [INFO] [stderr] warning: unopened HTML tag `em` [INFO] [stderr] --> src/generated.rs:2900:2172 [INFO] [stderr] | [INFO] [stderr] 2900 | ...Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head... [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: `rusoto_codebuild` (lib doc) generated 44 warnings [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.82s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/rusoto_codebuild/index.html [INFO] running `Command { std: "docker" "inspect" "cf07855aea73038b33ac4ff286c1a6ed42400ced23a15a117e23bc6033a17959", kill_on_drop: false }`