-
Improvement
-
Resolution: Fixed
-
Minor
-
-
5.0.0-beta2
I currently use the warnings plugin in a pipeline build by simply calling the build step. Doing this sets the build result to unstable, so I was checking that during the pipeline to determine whether some extra steps to run.
Specifically, I have a parallel build, which builds on multiple different configurations in parallel, and I want to rename the log file for each build to "unstable" only if that configuration got warnings. However, the build result is global for the whole pipeline. How can I obtain the number of warnings or the "result" of the warnings step in such a way that each parallel invocation can get its own results? This allows me to rename my logged files so that users who look at the final results can quickly determine which configurations were faulty?
- depends on
-
JENKINS-49938 Create a combined step that is compatible with Declarative Pipeline
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
-
JENKINS-38399 Number of new warnings not calculated correctly when using pipeline
-
- Resolved
-
- mentioned in
-
Page Failed to load
[JENKINS-40164] Obtain parallel warnings results in pipeline
| Link |
New:
This issue is related to |
| Link |
New:
This issue is related to |
| Link |
New:
This issue is related to |
| Summary | Original: warnings pipeline parallel obtian "results" | New: Obtain parallel warnings results in pipeline |
| Labels | New: analysis-core-2.0 |
| Remote Link | New: This issue links to "Page (Jenkins Wiki)" [ 17268 ] |
| Epic Link |
New:
|
| Component/s | New: analysis-core-plugin [ 15709 ] |
| Link |
New:
This issue depends on |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |