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 out of memory error when uploading the testcomplete results to confluence like wiki.
Attached the log files
- 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.
- 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
- cunderw6 years agoCommunity Hero
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.
- tristaanogre6 years agoEsteemed Contributor
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.
- nisgupta6 years agoValued Contributor
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 .
- cunderw6 years agoCommunity Hero
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.
Related Content
- 11 years ago
- 3 years ago
- 4 years ago
- 7 years ago
Recent Discussions
- 2 days ago