Google
×
This guide provides a small selection of best practices for pipelines and points out the most common mistakes. The goal is to point pipeline authors and ...
Missing: convert | Show results with:convert
This plugin allows tracking performance KPIs, based on results read from popular testing tools ( Apache JMeter, JUnit, Taurus).
Missing: history | Show results with:history
Existing properties set through the Jenkins UI for non-multibranch Pipelines will be preserved. properties. Array / List of Nested Choice of Objects; +
Pipeline Steps Reference. The following plugins offer Pipeline-compatible steps. Each plugin link offers more information about the parameters for each step ...
Missing: threshold | Show results with:threshold
This plugin allows tracking performance KPIs, based on results read from popular testing tools ( Apache JMeter, JUnit, Taurus).
Missing: history | Show results with:history
Nov 21, 2016 ˇ Because performance tuning is data driven, I'm going to use real-world data selected three very large Jenkins instances that I help support.
Missing: convert history
... threshold. Jenkins supports two types of nodes: agents (described below). built-in node. The built-in node is a node that exists within the controller process ...
Missing: convert history
2 days ago ˇ The default factor is 1.0. A factor of 0.0 will disable the test result contribution to build health score, and, as an example, a factor of 0.5 ...
Missing: convert performance threshold
The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps ...
Defines a limit for the characters shown in the description field for each build row in the Build History column. A positive integer (e.g. 300 ) will define ...
Missing: convert | Show results with:convert