To collect our test results and artifacts, we will use the post section. Jenkinsfile (Declarative Pipeline). pipeline { agent any stages { stage('Test') ...
Pipeline Steps Reference. The following plugins offer Pipeline-compatible steps. Each plugin link offers more information about the parameters for each step ...
As you might expect, setting environment variables per stage means they will only apply to the stage in which they're defined. Jenkinsfile (Declarative Pipeline).
Persist artifacts and console output for the specific number of recent Pipeline runs. For example: options { buildDiscarder(logRotator(numToKeepStr: '1 ...
Assuming everything has executed successfully in the example Jenkins Pipeline, each successful Pipeline run will have associated build artifacts archived, test ...
Once your Pipeline has completed, whether it succeeds or fails, you can go to the side panel for the run in the classic UI and click on "Restart from Stage".
Missing: /url | Show results with:/url
The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps ...
The step returns an array of file info objects who's properties you can see in the below example. Ex: def files = findFiles(glob: '**/TEST-*.xml') echo """${ ...
The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the ...
Existing properties set through the Jenkins UI for non-multibranch Pipelines will be preserved. properties. Array / List of Nested Choice of Objects