Don't save CI packages as artifacts (dotnet/core-setup#5508)
authorDavis Goodin <dagood@users.noreply.github.com>
Tue, 19 Mar 2019 17:30:36 +0000 (12:30 -0500)
committerGitHub <noreply@github.com>
Tue, 19 Mar 2019 17:30:36 +0000 (12:30 -0500)
Publishing to a build artifact can take long enough to time out the build, and isn't useful very often.

Commit migrated from https://github.com/dotnet/core-setup/commit/4d6b497d03a1758b9beed08a0b3fa258bc78160d

eng/jobs/bash-build.yml

index 9fff60b..fe3fada 100644 (file)
@@ -173,24 +173,6 @@ jobs:
       continueOnError: true
       condition: succeededOrFailed()
 
-    - task: CopyFiles@2
-      displayName: Copy packages to stage
-      inputs:
-        SourceFolder: '$(Build.SourcesDirectory)/bin/'
-        Contents: |
-          */packages/*
-        TargetFolder: '$(Build.StagingDirectory)\Packages'
-      continueOnError: true
-      condition: succeededOrFailed()
-
-    - task: PublishBuildArtifacts@1
-      displayName: Publish Artifact Packages
-      inputs:
-        PathtoPublish: '$(Build.StagingDirectory)\Packages'
-        ArtifactName: ${{ parameters.displayName }}-$(_BuildConfig)-Packages
-      continueOnError: true
-      condition: succeededOrFailed()
-
     - script: df -h
       displayName: Check space (df -h)
       condition: always()