ContributionsMost RecentMost LikesSolutionsRe: ReadyAPI Runner on Jenkins writes logs in the home directory how do I clean up? Hi Rao, Thank you for pointing this out. The linked thread has a different problem. The system.out and system.err is perfectly written to the jenkins logfiles. The logs that are written to the hidden directory <home>/.readyapi are totally useless for me since I have system.out and system.err. If I could I woult deactivate this redundant log location but I got the impression that this cannot be done. Thanks Carsten Re: ReadyAPI Runner on Jenkins writes logs in the home directory how do I clean up? Hi, moving the home directory will effect other installed software, so this is not an option. Isn't this a problem for everyone, that the runner will create a hidden directory which will grow for ever without the possibility of cleaning it up? We set up the automation hosts automatically and no one is meant actually log on to it. Thx Carsten ReadyAPI Runner on Jenkins writes logs in the home directory how do I clean up? We use a ReadyAPI Runner on our Jenkins slave and we have seen that the runner writes his own log for every Job that it running. The log is located in the <home directory>/.readyapi directory, where we have a reduced space to write something. After a while the node will be unusable because the logfiles will exceed the space available. In the documentation I did not find an option to specify not to write logs there or a different location. How can I tell the runner not to write logs or write them elsewhere? I'm running on linux, the used readyapi version is at 2.6.0 at the moment. SolvedRe: Jenkins does not recognize ReadyApi maven plug-in test failures as unstable build Thanks for the answer, JustinM89. But this does not adress my problem. I don't want the build to fail if a test fails, I want the build to be marked as unstable. Please consider the Jenkins terminology here: https://wiki.jenkins.io/display/JENKINS/Terminology Thanks Carsten Jenkins does not recognize ReadyApi maven plug-in test failures as unstable build We're using Ready Api 2.3.0 with the ready-api-maven-plugin 2.3.0 to run our tests, which works fine. Although some tests fail, Jenkins does not recognice the build as unstable, as it should when tests are failing. ReadyAPI 2.3.0 TestCaseRunner Summary ----------------------------- Time Taken: 16172ms Total TestSuites: 0 Total TestCases: 2 (2 failed) Total TestSteps: 686 Total Request Assertions: 5 Total Failed Assertions: 0 Total Exported Results: 2 19:40:57,286 INFO [SoapUIProTestCaseRunner] Created report at file:/C:/vhvEntw/Jenkins/workspace/Testautomatisierung/SOAP_UI_Vertrieb/Vertrieb_SoapUI_TAA_Kfz_S/poms/kfz/s/target/TestOutput/index.html [INFO] ReadyAPI 2.3.0 shutting down [JENKINS] Zeichne Testergebnisse auf [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 47.889 s [INFO] Finished at: 2019-07-25T19:40:57+02:00 [INFO] Final Memory: 78M/1189M [INFO] ------------------------------------------------------------------------ Here's the config that writes the results to the default maven location: <configuration> <projectFile> ../../../services/kfz/auto/TarifrechnerWS_KFZTarifrechnerService_v0118 </projectFile> <projectProperties> <value>taa_endpoint=${#Project#taa_Endpoint_S}</value> <value>Verarbeitungsebene=S</value> </projectProperties> <testCase>Regression Tarif 01.10.18</testCase> <junitReport>true</junitReport> <testFailIgnore>true</testFailIgnore> <printReport>true</printReport> <reports>${basedir}/target/surefire-reports</reports> <outputFolder>${basedir}/target/TestOutput</outputFolder> </configuration> content: Does anyone have an idea why Jenkins does not consider this build as unstable? This works when using the soapui-maven-plugin the same way... Thanks Carsten Solved