我通过以下三个步骤将功能应用发布到Azure Pipeline中的工件:
- task: DotNetCoreCLI@2
displayName: 'dotnet publish function app'
inputs:
command: publish
arguments: '--configuration Release --output updater_publish_output'
projects: 'Service/XYZ/Hosts.FA/*.csproj'
publishWebProjects: false
modifyOutputPath: false
zipAfterPublish: false
- task: ArchiveFiles@2
displayName: 'archive function app files'
inputs:
rootFolderOrFile: "$(System.DefaultWorkingDirectory)/updater_publish_output"
includeRootFolder: false
archiveFile: "$(System.DefaultWorkingDirectory)/Hosts.FA.zip"
- task: PublishBuildArtifacts@1
displayName: 'publish function app files'
inputs:
PathtoPublish: '$(System.DefaultWorkingDirectory)/Hosts.FA.zip'
ArtifactName: '$(Build.BuildNumber)'
这是项目结构:
我已将第一步更新为:
- name: dotnet publish function app
run: dotnet publish Service/XYZ/Hosts.FA/Hosts.FA.csproj --configuration Release --output updater_publish_output
如何将ArchiveFiles @ 2和PublishBuildArtifacts @ 1任务转换为GitHub Actions?
答案 0 :(得分:2)
从以下位置使用Upload-Artifact
任务:https://github.com/actions/upload-artifact。它将替换ArchiveFiles@2
(压缩)和PublishBuildArtifacts@1
(上传)。
- uses: actions/upload-artifact@v2
with:
name: ${{github.run_number}}
path: |
updater_publish_output
根据https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#github-context github.run_number
是
存储库中特定工作流程的每次运行的唯一编号。对于工作流程的第一次运行,此数字从1开始,并在每次新运行时递增。如果您重新运行工作流运行,此数字不会更改。
您还可以使用github.run_id
:
存储库中每次运行的唯一编号。如果您重新运行工作流运行,此数字不会更改。