Updated usage of `pip` in the package build template. (#6223)

.pipelines/templates/PackageBuild.yml

@@ -103,6 +103,12 @@ steps:
     parameters:
       buildRepoRoot: ${{ parameters.buildRepoRoot }}
 
+  - ${{ if parameters.pipArtifactFeeds }}:
+      - task: PipAuthenticate@1
+        inputs:
+          artifactFeeds: "${{ parameters.pipArtifactFeeds }}"
+        displayName: "Authenticate to custom pip artifact feeds"
+
   - ${{ if parameters.customToolchainArtifactName }}:
       - task: DownloadPipelineArtifact@2
         displayName: "Download toolchain"
@@ -214,4 +220,3 @@ steps:
           buildRepoRoot: ${{ parameters.buildRepoRoot }}
           failOnTestFailures: ${{ parameters.failOnTestFailures }}
           outputArtifactsFolder: ${{ parameters.outputArtifactsFolder }}
-          pipArtifactFeeds: ${{ parameters.pipArtifactFeeds }}

.pipelines/templates/PackageTestResultsAnalysis.yml

@@ -14,9 +14,6 @@ parameters:
     type: string
     default: "$(Build.ArtifactStagingDirectory)"
 
-  - name: pipArtifactFeeds
-    type: string
-
   # Local constants. Can't use variables in a template without jobs or stages.
   - name: reportFileName
     type: string
@@ -27,12 +24,6 @@ parameters:
     default: "$(Agent.TempDirectory)"
 
 steps:
-  - ${{ if parameters.pipArtifactFeeds }}:
-      - task: PipAuthenticate@1
-        inputs:
-          artifactFeeds: "${{ parameters.pipArtifactFeeds }}"
-        displayName: "Authenticate to custom pip artifact feeds"
-
   - bash: |
       pip3 install junit_xml
     displayName: "Install Python dependencies"