Remove drop-nuget artifact from all pipelines (#18592)

### Description
Currently, the `drop-nuget` artifact only contains protoc.exe which is
also part of the `drop-extra` artifact.



### Motivation and Context
<!-- - Why is this change required? What problem does it solve?
- If it fixes an open issue, please link to the issue here. -->
This commit is contained in:
Jian Chen 2023-11-28 13:23:01 -08:00 committed by GitHub
parent e24733cfe9
commit a49f31b670
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 17 deletions

View file

@ -3,7 +3,7 @@ parameters:
NugetPackageName : ''
ArtifactSuffix: ''
StageSuffix: 'CPU'
# For inference packages, the test data artifact name is drop-nuget and no suffix is required.
# For inference packages, the test data artifact name is drop-extra and no suffix is required.
# For training packages, to differentiate the artifact name we add '-training' suffix. This needs to be passed from
# the parent pipeline.
TestDataArtifactSuffix: ''
@ -64,12 +64,6 @@ stages:
artifactName: drop-signed-nuget-${{ parameters.ArtifactSuffix }}
targetPath: '$(Build.BinariesDirectory)\nuget-artifact'
- task: DownloadPipelineArtifact@0
displayName: 'Download Pipeline Artifact - testdata'
inputs:
artifactName: 'drop-nuget${{ parameters.TestDataArtifactSuffix }}'
targetPath: '$(Build.BinariesDirectory)\testdata'
- template: get-nuget-package-version-as-variable.yml
parameters:
packageFolder: '$(Build.BinariesDirectory)\nuget-artifact'

View file

@ -206,8 +206,7 @@ stages:
artifactName: 'drop-onnxruntime-nodejs-win-${{ parameters.packageName }}'
DoEsrp: ${{ parameters.DoEsrp }}
# Upload protoc.exe, which will be used in nuget build for generating C# files
# TODO: We need to make this step independent of the packageName, so that it can be used in test_win.yml
#Upload protoc.exe, which will be used in nuget build for generating C# files
- task: PublishPipelineArtifact@1
displayName: Publish protoc as drop-extra
condition: and(succeeded(), or(eq('${{ parameters.packageName}}', 'x64'), eq('${{ parameters.PublishProtoc}}', true)))
@ -224,14 +223,6 @@ stages:
Contents: 'custom_op_library.dll'
TargetFolder: '$(Build.ArtifactStagingDirectory)/testdata'
#To be used in test_win.
# TODO: Do we need to publish protoc twice?
- task: PublishPipelineArtifact@1
condition: and(succeeded(), or(eq('${{ parameters.packageName}}', 'x64'), eq('${{ parameters.PublishProtoc}}', true)))
inputs:
targetPath: '$(Build.BinariesDirectory)\RelWithDebInfo\installed\bin\protoc.exe'
artifactName: 'drop-nuget${{ parameters.artifact_name_suffix }}'
- task: CmdLine@2
condition: and(succeeded(), eq('${{ parameters.buildJava}}', true))
displayName: 'Add symbols and notices to Java'