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.
Let's you limit the number of events posted to the test complete log.
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 .
You can specify how far back the events will be captured when an error occurs which is the crucial piece. You can aslo include more verbose log messages, or completely eclude all images. You could also split up your tests into multiple projects. There are plenty of options to reduce the size.
So, you're using the logs of the tests to instruct end users how to use the application? Or are you trying to give the users confidence that TestComplete is performing the tests accurately? I'm not sure I understand why the functional users (who are not the testers) need that much detail in the TC logs.
Functional users already know how to use the applications. The goal is to let the functional users know about the behavior of the application . The best way we can show them to submit the report in MHT format which show the information similar to manual actions .
I am little bit confused as we can see the same MHT test report in jenkins itself. the size of the MHT test report in Jenkins is same as the the size of the MHT report we are exporting at the end of the tests. Then why Jenkins gives the error ?
The error is occuring when you are trying to update the file via the confluence publisher. This looks to be a limitation of that plugin. See https://issues.jenkins-ci.org/browse/JENKINS-18383
You could talk with your infratstructue team and see if increase the memory allocation of the JVM fixes this, but my guess is you will still run into issues unless you decrease the size of your log file.