The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Any way to disable test scanning on "tear down"?

Deleted user
April 4, 2019

For my Gradle based pipeline I see stripped stack traces for failed test without any console logging context.

 

Java stack traces contains the most important info at the bottom and this part is stripped ((

 

It takes 3 min to collect/parse *test/*.xml report files while total build/test execution time of Gradle itself is 5 min.

 

So test report scan feature is useless and time consuming.

 

How can I disable this "feature"?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Philip Hodder
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 2, 2019

Hello Oleksandr,

Currently you cannot disable the test reporting feature. The closest workaround would be to remove the files before the build finishes, which will make the parser not find any files to parse.

Can you open a feature request with some more details about the size of your stack trave here: https://bitbucket.org/site/master/issues/new

Thanks,

Phil

TAGS
AUG Leaders

Atlassian Community Events