Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Linting visual


Hey all,

In bitbucket pipelines if you use a tool like junit you can make a special test report file like test-reports/junit.xml and you get this neat little tab (if any tests failed) that shows the failed test and their details.


Now I've been looking all over, but can't find anything about it. (Probably looking incorrectly).

But I want this tab for my 'failed' linting as well. We run a pipeline in which we run both unittests and linting. But the test tab now kind of obfuscates the linting failures.

Is there a way to also have a tab for linting? Or a custom tab you can completely define the output for yourself?


(EDIT: I just found that maybe the linting can go into junit format as well. If that's the case, is it possible to have two 'test' tabs?)

1 answer

1 accepted

For now i've solved it by creating a separate junit.xml in a separate folder inside test-reports. (for example /test-reports/linting/junit.xml)

All the errors appear in the test tab as 1 single failure. ng lint creates its own 'suite' so they just show at the top.

It's good enough for me, although it would be nice to have like a tab called 'linting'


I'll accept my own answer if no-one comes with a better solution within the next ~5 days.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events