Error: Repository can not be found. when trying to generate living docs in Azure DevOps release pipeline

Answered

John Cross-Martin

• June 23, 2022 15:57
• Edited

Hi,

I do hope someone can help with a problem I've been battling for days...

We have three ADO projects, each one with a release pipeline that runs SpecFlow tests and then generates living documentation using the ADO extension.

Two of these project pipelines work fine, the other however keeps throwing the following error:

##[error]Error: Repository can not be found. If the build task is used in a Release pipeline, a valid 'Build' artifact reference should be added in the release definition.

    at D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:85:31

    at step (D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:44:23)

    at Object.next (D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:25:53)

    at D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:19:71

    at new Promise (<anonymous>)

    at __awaiter (D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:15:12)

    at D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:77:12

    at Object.<anonymous> (D:\agent\_work\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.964\index.js:172:3)

    at Module._compile (internal/modules/cjs/loader.js:778:30)

    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)

 

The pipeline does have a valid build artefact as you can see from the screenshot below. The artefact is also used without problem in the task that precedes the doc generation task to run the tests.

I have enabled System.Debug = true in the pipeline but I don't think it's offered anything else useful. Happy to supply that output if necessary.

I can see from the debug output that TestExecution.json is successfully generated from the test run. Framework is .Net Core 3.1

 

Any help/suggestions on how to resolve this will be greatly received.

0

• 

  Andreas Willich

  • June 27, 2022 13:01

  No quick clue what is happening to you. 

  Are you using the latest version of the SpecFlow+LivingDoc Plugin?

  Is there a difference between the repositories for which the builds are?

  0
• 

  John Cross-Martin

  • June 27, 2022 15:55

  Hi, yes I'm using latest version of NuGet package (3.9.57) in my .Net test project and latest ADO extension version (0.6.964). It's the same versions in each of the ADO projects. I can't see any difference in the repositories.

  Are there any particular permissions that the doc generation requires to run in ADO? 

  0
• 

  John Cross-Martin

  • August 05, 2022 13:44

  For anyone else who runs into this, it was resolved by disabling this setting on the Azure DevOps project:

  Protect access to repositories in YAML pipelines 

  0

Please sign in to leave a comment.