Skip to content

Commit 8682579

Browse files
authored
Use different API key (microsoft#2152)
* Try publish symbols task for pipeline instead of Microbuild task * Use different API key
1 parent 8c012ac commit 8682579

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

build/azure-pipeline-steps.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,13 +94,16 @@ steps:
9494
SymbolServerType: 'TeamServices'
9595
condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'), eq('${{ parameters.OSTarget }}', 'any'), eq(variables['ShouldPublishNuget'], 'True'), eq(variables['SignType'], 'real'))
9696

97+
# If API key expires, you need to generate a new one here:
98+
# https://www.nuget.org/account/apikeys
99+
# You'll need admin permission to associate the key with the Python Tools org
97100
- task: NuGetCommand@2
98101
displayName: 'NuGet publish parsing '
99102
inputs:
100103
command: push
101104
packagesToPush: '$(Build.ArtifactStagingDirectory)/**/Microsoft.Python.Parsing*.nupkg;!$(Build.ArtifactStagingDirectory)/**/*.symbols.nupkg'
102105
nuGetFeedType: external
103-
publishFeedCredentials: 'rchiodo_nuget'
106+
publishFeedCredentials: 'python_language_server_nuget'
104107
condition: and(succeeded(), eq(variables['ShouldPublishNuget'], 'True'), eq('${{ parameters.OSTarget }}', 'any'), notin(variables['Build.Reason'], 'PullRequest'))
105108
timeoutInMinutes: 20
106109

0 commit comments

Comments
 (0)