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.
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.
You're getting an out of memory error, which probably means your mht is way too big. I would look into Log.LockEvents(); to reduce the number of events being logged and images which is likely what's causing the huge file size.
MHT file always generates in the Jenkins master node whereas job runs on the Slave node. Post-build will be triggered in the slave.
Before triggering the upload results to Confluence, MHT needs to be placed in the workspace of Slave from Master node. No plug-ins found to copy the file from Master node to salve workspace after a build.
Me too having the same kind of problem, I'm trying to solve it. Hope will find a solution soon.
Yes you are right till now we have not find the way to copy the MHT file from master node to slave node.
So what I did is Through testcomplete script I am exporting the MHT log . But there is issue jenkins build willl not post the MHT file to confluence or wiki if there are errors in the script. If there are no errors then it will post the MHT file to confluence
I have just attached the Post build actions - where I am using plugin Publish to confluence . Other attachment is related to console log showing the script has errors and jenkins detects it as unstable due to which MHT file do not get published to confluence.
I am not sure do we have any limitation in jenkins confluence publisher plugin ?