##[error]Unable to locate executable file: 'tar'.

[KristofKuli]

Since Allure extension has been updated to version 1.2.0, the target path configuration has been changed from "reportDir" to "testResultsDir" and we are getting the following error message:
##[error]Unable to locate executable file: 'tar'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.

We are not sure, if the issue is with the target path definition or with the new version itself. The full log can be found below.

Starting: Publish allure report
==============================================================================
Task         : Publish Allure Report
Description  : Task for generate and publish Allure Report
Version      : 1.2.0
Author       : Qameta Software Inc.
Help         : Generate and publish Allure Report
==============================================================================
AllureReport input: {
  allureVersion: '2.26.0',
  testResultsDir: 'D:\\build\\V1\\_w\\1\\s\\res-cukes-rest-tests-arena-testsandbox\\target\\site\\allure-maven-plugin',
  reportDir: 'D:\\build\\V1\\_w\\1\\s\\c9462aee-fb03-467c-83ca-7564fe9fbc9a'
}
Found 10 test results files.
Downloading: https://github.com/allure-framework/allure2/releases/download/2.26.0/allure-2.26.0.tgz
Extracting archive
Error: Unable to locate executable file: 'tar'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
    at Object._which (D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\node_modules\azure-pipelines-task-lib\internal.js:323:23)
    at new ToolRunner (D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\node_modules\azure-pipelines-task-lib\toolrunner.js:31:29)
##[error]Unable to locate executable file: 'tar'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
    at Object.tool (D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\node_modules\azure-pipelines-task-lib\task.js:1282:14)
    at D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\tool.js:468:21
    at Generator.next (<anonymous>)
    at D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\tool.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\tool.js:4:12)
    at extractTar (D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\node_modules\azure-pipelines-tool-lib\tool.js:463:12)
    at D:\build\V1\_w\_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\1.2.0\index.js:50:53
Finishing: Publish allure report

[epszaw]

There wasn't any change related to the code that downloads allure and creates an executable from it.

The process doesn't have access to tar executable, so it could happen when the PATH variable was modified. Did you change them in the pipeline configuration?

[KristofKuli]

Hi Konstatin,
There's no modification is being done in the pipeline, regarding the PATH variable.

[epszaw]

Replaced azure tool utility by the tar node module in the 1.2.2 version of the extension. Could you try to run the pipeline once more and verify the result?

[KristofKuli]

With the new version, there's no errors and the pipelines finished successfully. However, the Tests tab displays all the passed tests, while navigating to the Allure Report tab, it doesn't show any result.
Tests:

Allure Report:

The generated reports are available as build artifacts.

[epszaw]

Could you check testResultsDir input value? Does it point to a directory with Allure Results?

[KristofKuli]

Sorry, I have missed to add this part:
What can be seen in the logs:

testResultsDir: 'D:\build\V1\_w\1\s\res-cukes-rest-tests-arena-testsandbox\target\site\allure-maven-plugin',
reportDir: 'D:\build\V1\_w\1\s\'
Seems reportDir is not correct, because report is generated under
'D:\build\V1\_w\1\s\res-cukes-rest-tests-arena-testsandbox\target\site\allure-maven-plugin'

[epszaw]

reportDir generates dynamically for each task run.

The extension generates the report automatically, so you need just to pass the correct path to allure results directory.

In your case, just check, where the directory is located locally and then, pass the relative path from the project's root to the directory into testResultsDir.

[KristofKuli]

From logs:
Report successfully generated to D:\build\V1_w\1\s\res-cukes-rest-tests-arena-testsandbox\target\site\allure-maven-plugin

Task:
- task: PublishAllureReport@1
displayName: 'Publish allure report'
condition: succeededOrFailed()
inputs:
testResultsDir: 'res-cukes-rest-tests-arena-testsandbox/target/site/allure-maven-plugin'

[trushechinam]

Please let me know on what task I am hangling aditionally allure-results directory?
From my pipeline:

• task: Maven@3
  displayName: 'ARENA_1 Generate Allure report'
  condition: succeededOrFailed()
  inputs:
  mavenPomFile: 'res-cukes-rest-tests-arena-testsandbox/pomFirst.xml'
  javaHomeOption: 'JDKVersion'
  jdkVersionOption: '1.11'
  jdkArchitectureOption: 'x64'
  goals: 'allure:report'

Gives such result:

To be sure that directory and generated report is correct I have created another task, to save report data:

- task: PublishPipelineArtifact@1
  displayName: 'Publish all files'
  condition: succeededOrFailed()
  inputs:
    targetPath: res-cukes-rest-tests-arena-testsandbox/target/site/allure-maven-plugin
    artifactName: Allure_report_All

I am able to download and open report locally
And it is what I see

It means that report was generated correctly and issue is with task to publish it, directly this one:

• task: PublishAllureReport@1
  displayName: 'Publish allure report'
  condition: succeededOrFailed()
  inputs:
  testResultsDir: 'res-cukes-rest-tests-arena-testsandbox/target/site/allure-maven-plugin'

What for some reason do not show correct report data

[trushechinam]

Could be "testResultsDir" in my case should have another path, could be it should contain index.html file? Because it seems it doesn't understand the path specified, and do not find there results

[ciconq]

Hey @trushechinam, maybe try adding this task for fetching the actual allure-results path, I am using it before the publish Allure report task.

      - task: PowerShell@2
        displayName: 'Get allure-results path'
        condition: succeededOrFailed()
        inputs:
          targetType: 'inline'
          script: |
            $selectedFolder = Get-ChildItem -Path $(System.DefaultWorkingDirectory) -Recurse -Filter "allure-results" -Directory | Select-Object -First 1
            Write-Output "Selected folder: $($selectedFolder.FullName)"
            Write-Output "##vso[task.setvariable variable=allureResultsPath]$($selectedFolder.FullName)"

      - task: PublishAllureReport@1
        displayName: 'Publish Allure report'
        condition: succeededOrFailed()
        inputs:
          allureVersion: '2.27.0'
          testResultsDir: '$(allureResultsPath)'

[trushechinam]

Hello, I have added tasks what you have proposed
What I get:
Selected folder: D:\build\V1_w\1\s\res-cukes-rest-tests-arena-testsandbox\target\allure-results

And finally report have been generated.
I would say that it is PublishAllureReport@1 task issue that it doesn't understand testResultsDir: 'res-cukes-rest-tests-arena-testsandbox/target/site/allure-maven-plugin' as

• it used to work before
• all other tasks are working correctly with such path specified.

Thank you for help,
Marina.

[KristofKuli]

Hi All,

Thank you for the help. Marina confirmed that the extension if working fine for her, so we can close this Issue.

Best regards,
Kristof