tabName seems to not work

[agrspyro]

Hello,
tabName parameter seems to not work - tab names are always named as 'run-tests #1' not matter that different text is used in parameter.

Task example:

• task: PublishHtmlReport@1
  displayName: Publish iOS Report
  inputs:
  reportDir: '$(Build.ArtifactStagingDirectory)/iOS_Report.html'
  tabName: 'iOSReport'

Task result:

[bkarakashev]

It doesn't work for me either, also if I set the path to dir with HTML in reportDir it doesn't pick up the file I have to set the exact path to a file.

[goyalg8]

Hi, I am using this extension in release pipeline but still HTML tab is not appearing. Can you please help me with at least HTML tab can appear in azure devops

[hoani]

I believe this is due to line:

azure-pipeline-html-report/src/tabContent.tsx

Line 124 in c56938b

const name = metadata[2] !== '__default' ? `${metadata[2]} #${metadata[3]}` : metadata[0]

When it's a multi stage build, it adds a count, however this logic also uses the stage name instead of the tab name.

It probably needs to be:

        const name = metadata[2] !== '__default' ? `${metadata[0]} #${metadata[3]}` : metadata[0]

So that it names the tab <tabname> #1 thoughts @JakubRumpca ? Happy to PR this if you agree?

[ericstrong89]

having same issue. do we know if a fix was ever implemented?

[vladkuperman-payroc]

Accidently discovered a workaround. Prefix the tab name string with two dots:

tabName: ..DesiredTabName

[RHSolita]

Accidently discovered a workaround. Prefix the tab name string with two dots:

tabName: ..DesiredTabName

This works as desired. Thanks for the workaround!
For anyone wondering, this is the syntax we are using now:

• task: PublishHtmlReport@1
  displayName: 'Dependency vulnerabilities'
  inputs:
  tabName: '..Dependency vulnerabilities'
  reportDir: '$(Build.SourcesDirectory)/target/dependency-check-report.html'