Single file from Wiki PDF export

[WebGoose]

I'm really struggling with the path for exporting a single page from the Wiki to PDF in my release.

In the steps before I use your other tasks to generate release notes and commit to the Wiki in Devops which works perfectly. I'm trying now to export that release note entry to PDF so that I can email it out.

Where am I going wrong with the path to the individual file? I feel like I've tried every possible permutation and I'm starting to lose my mind :) I'm probably just misunderstanding the instructions.

This is how the wiki looks

This is what the root folder looks like when you clone the wiki. The folder structure to the file goes /Releases/QA/file.md

This is how I have the task set up

And this is the error I'm getting.

The wiki update task is working and adding the item and when I clone the repo the file is there so I'm not sure where I'm going wrong with the path to it.

Any help would be greatly appreciated.

Thank you!

[rfennell]

I think the confusion is that there are two ways the task can work, probably down to my documentation not being clear enough.

I had always assumed then when in single file mode a WIKI repo would not be cloned. The task would just be using the output from another task. This is my test case for that scenario

    - task: richardfennellBM.BM-VSTS-XplatGenerateReleaseNotes-DEV1.XplatGenerate-Release-Notes.XplatGenerateReleaseNotes@2
      displayName: 'Generate Release Notes based on Release Comparision API'
      inputs:
        outputfile: '$(System.DefaultWorkingDirectory)\inline.md'
        outputVariableName: OutputText
        templateLocation: InLine
        inlinetemplate: |
          # Release notes 
          **Build Number**  : ${buildDetails.buildNumber} 
          **Build started** : ${buildDetails.startTime}  
          **Source Branch** : ${buildDetails.sourceBranch}  
          
          ### Associated work items  
          @@WILOOP@@  
          * ** ${widetail.fields['System.WorkItemType']} ${widetail.id} ** Assigned by: ${widetail.fields['System.AssignedTo']}  ${widetail.fields['System.Title']}  
          @@WILOOP@@  
            
          ### Associated commits
          @@CSLOOP@@  
          * **ID ${csdetail.commitId} ** ${csdetail.comment}    
          @@CSLOOP@@
    - task: richardfennellBM.BM-VSTS-WikiPDFExport-Tasks-DEV.WikiPDFExportTask.WikiPdfExportTask@1
      displayName: 'Export Single File'
      inputs:
        cloneRepo: false
        localpath: '$(System.DefaultWorkingDirectory)'
        singleFile: 'inline.md'
        outputFile: '$(Build.ArtifactStagingDirectory)\PDF\singleFile.pdf'

That said, there is no reason you should not do a clone if you wish and name a single file, you just make sure the clone path and the file path match up.

Also you can export all or part of a WIKI repo as you wish, as these fragments show

    - task: richardfennellBM.BM-VSTS-WikiPDFExport-Tasks-DEV.WikiPDFExportTask.WikiPdfExportTask@1
      displayName: 'Export Azure DevOps WIKI'
      condition: succeededOrFailed()
      inputs:
        cloneRepo: true
        repo: 'https://dev.azure.com/richardfennell/GitHub/_git/GitHub.wiki'
        useAgentToken: true
        outputFile: '$(Build.ArtifactStagingDirectory)\PDF\Azrepo.pdf'
    - task: richardfennellBM.BM-VSTS-WikiPDFExport-Tasks-DEV.WikiPDFExportTask.WikiPdfExportTask@1
      displayName: 'Export part of the Azure DevOps WIKI'
      condition: succeededOrFailed()
      inputs:
        cloneRepo: true
        repo: 'https://dev.azure.com/richardfennell/GitHub/_git/GitHub.wiki'
        useAgentToken: true
        outputFile: '$(Build.ArtifactStagingDirectory)\PDF\AzrepoFilter.pdf'
        localpath: '$(System.DefaultWorkingDirectory)\repopartial'
        rootExportPath: '$(System.DefaultWorkingDirectory)\repopartial\folder'

A good tip if you are having problems is to run the pipeline on a private agent that you can RDP onto so you can see the file path, or drop a CMD/PowerShell/BASH script block in the pipeline that does a directory listing the log

[WebGoose]

Thank you so much for the detailed reply. It dawned on me just after I posted the question that there was an option to just select the file generated by your Release Notes task in the working directory instead of cloning. I tried that and it worked first time! I'm a real beginner when it comes to azure DevOps. Thanks again for taking the time to reply.

…

On Sun, 07 Feb 2021, 20:36 Richard Fennell, ***@***.***> wrote: I think the confusion is that there are two ways the task can work, probably down to my documentation not being clear enough. I had always assumed then when in single file mode a WIKI repo would not be cloned. The task would just be using the output from another task. This is my test case for that scenario - task: ***@***.*** displayName: 'Generate Release Notes based on Release Comparision API' inputs: outputfile: '$(System.DefaultWorkingDirectory)\inline.md' outputVariableName: OutputText templateLocation: InLine inlinetemplate: | # Release notes **Build Number** : ${buildDetails.buildNumber} **Build started** : ${buildDetails.startTime} **Source Branch** : ${buildDetails.sourceBranch} ### Associated work items @@WiLoop@@ * ** ${widetail.fields['System.WorkItemType']} ${widetail.id} ** Assigned by: ${widetail.fields['System.AssignedTo']} ${widetail.fields['System.Title']} @@WiLoop@@ ### Associated commits @@Csloop@@ * **ID ${csdetail.commitId} ** ${csdetail.comment} @@Csloop@@ - task: ***@***.*** displayName: 'Export Single File' inputs: cloneRepo: false localpath: '$(System.DefaultWorkingDirectory)' singleFile: 'inline.md' outputFile: '$(Build.ArtifactStagingDirectory)\PDF\singleFile.pdf' That said, there is no reason you should not do a clone if you wish and name a single file, you just make sure the clone path and the file path match up. Also you can export all or part of a WIKI repo as you wish, as these fragments show - task: ***@***.*** displayName: 'Export Azure DevOps WIKI' condition: succeededOrFailed() inputs: cloneRepo: true repo: 'https://dev.azure.com/richardfennell/GitHub/_git/GitHub.wiki' useAgentToken: true outputFile: '$(Build.ArtifactStagingDirectory)\PDF\Azrepo.pdf' - task: ***@***.*** displayName: 'Export part of the Azure DevOps WIKI' condition: succeededOrFailed() inputs: cloneRepo: true repo: 'https://dev.azure.com/richardfennell/GitHub/_git/GitHub.wiki' useAgentToken: true outputFile: '$(Build.ArtifactStagingDirectory)\PDF\AzrepoFilter.pdf' localpath: '$(System.DefaultWorkingDirectory)\repopartial' rootExportPath: '$(System.DefaultWorkingDirectory)\repopartial\folder' A good tip if you are having problems is to run the pipeline on a private agent that you can RDP onto so you can see the file path, or drop a CMD/PowerShell/BASH script block in the pipeline that does a directory listing the log — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#942 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGKZQDKMEONZLWW3MDSSITS53MSJANCNFSM4XHUI77A> .