Forum Discussion

nisgupta's avatar
nisgupta
Valued Contributor
7 years ago

TestExecute Integration With Jenkins

  We are looking for the ways - how Jenkins can run the projects located in TestExecute machines. Here is our case. At this now now Source code management and so no git.  Jenkins is set up on m...
nisgupta's avatar
nisgupta
Valued 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

 

cunderw's avatar
cunderw
Community Hero
7 years ago

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. 

  • nisgupta's avatar
    nisgupta
    Valued Contributor
    7 years ago

    cunderw

     

    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 ?

  • cunderw's avatar
    cunderw
    Community Hero
    7 years ago

    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.