Forum Discussion
No, We have to use the external plug-in (like you are using currently) to do the upload or other kinds of stuff.
ok
I am concerned about the path of the MHT file on master jenkins. Attached the screenshot with the path.
Thanks
NG
- shankar_r6 years agoCommunity Hero
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.
-
- cunderw6 years agoCommunity Hero
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.
- shankar_r6 years agoCommunity Hero
Things to note here,
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.
- nisgupta6 years agoValued Contributor
Thank you
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 ?
Thanks
NG
- nisgupta6 years agoValued Contributor
We are getting when uploading the testcomplete result - MHT to confluence like wiki
Attach the log file.
- nisgupta6 years agoValued Contributor
We are getting when uploading the testcomplete result - MHT to confluence like wiki
Attach the log file.
- nisgupta6 years agoValued Contributor
we are getting out of memory error when uploading the testcomplete results to confluence like wiki.
Attached the log files
- cunderw6 years agoCommunity Hero
Let's you limit the number of events posted to the test complete log.
- nisgupta6 years agoValued Contributor
Ok,
I got this. This is how we can limit the logging.
We have a case here
Our functional users want to see the results in MHT format which is the best way . The functional users do not have the knowledge of TestComplete. They want to see the how the application behave and from the start to end of the test case.
My concerns is limiting the logging will not allow the functional users to miss some steps .
Thanks
Nishchal
Related Content
- 11 years ago
- 3 years ago
- 4 years ago
- 7 years ago
Recent Discussions
- 2 days ago