Forum Discussion
It is not the Jenkins confluence publisher plugin limitation.
The default rule for Jenkins is, each build step checks the previous step status if it is not SUCCESS then it won't go to next build/post build step and it stops where an error occurs. Some plug-ins might have override options so that irrespective of previous step status it will run.
From Document:
-
Action on warnings - Specifies whether Jenkins should mark the entire build as failed or unstable when the TestComplete test log contains warnings.
-
Action on errors - Specifies whether Jenkins should mark the entire build as failed or unstable when the TestComplete test log contains errors.
Answer to question is,
Make the two drop-down boxes in the TestComplete build step advanced options to None as like below image then you are all set.
We are getting when uploading the testcomplete result - MHT to confluence like wiki
Attach the log file.
Related Content
- 11 years ago
- 3 years ago
- 8 years ago
- 4 years ago