×
The goal is to point pipeline authors and maintainers towards patterns that result in better Pipeline execution and away from pitfalls they might otherwise ...
Missing: ressources threshold
The post section defines one or more additional steps that are run upon the completion of a Pipeline's or stage's run (depending on the location of the post ...
Missing: ressources history
Give a build result to monitor for the selected job. ... Limit job run to certain ... SUCCESS: the build will rerun if the previous result was worse than SUCCESS ...
Missing: ressources history
Mar 22, 2024 · Trigger downstream pipeline that depend on Maven artifact generated by upstream pipelines. ... Threshold based on the status of the upstream ...
Missing: ressources history
When this option is configured, Jenkins can provide useful information about test results, such as historical test result trends, a web UI for viewing test ...
Missing: ressources | Show results with:ressources
The result of this action is a string [build-history-manager] which is prepend to job description. Use this action as long as the final result of condition ...
Missing: ressources | Show results with:ressources
Pipeline Steps Reference. The following plugins offer Pipeline-compatible steps. Each plugin link offers more information about the parameters for each step ...
Missing: ressources threshold
The build status degrades to unstable (or failed) if branch coverage decreases by more than this delta threshold compared to the previous build.
Missing: ressources history
Sep 18, 2023 · In the project/build page you can see a summary of passed/fail tests as well as passed/fail configuration methods. It also lists the failed test ...
Missing: ressources history
This step records coverage results of JaCoCo with the default file name pattern. The coverage information is rendered with the source code for every build, and ...
Missing: ressources | Show results with:ressources