-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Start using new packages.microsoft.com cli #20141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml
Show resolved
Hide resolved
tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml
Outdated
Show resolved
Hide resolved
tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml
Show resolved
Hide resolved
| SkipPublish = $${{ parameters.skipPublish }} | ||
| } | ||
| $params | Out-String -width 9999 | write-Verbose -Verbose | ||
| & '$(Pipeline.Workspace)/tools/packages.microsoft.com/releaseLinuxPackages.ps1' -MappingFilePath '$(System.DefaultWorkingDirectory)/tools/packages.microsoft.com/mapping.json' @params |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps we should change the path in the tools repo so when it's merged we don't break the servicing branches
| SkipPublish = $${{ parameters.skipPublish }} | ||
| } | ||
| $params | Out-String -width 9999 | write-Verbose -Verbose | ||
| & '$(Pipeline.Workspace)/tools/packages.microsoft.com/releaseLinuxPackages.ps1' -MappingFilePath '$(System.DefaultWorkingDirectory)/tools/packages.microsoft.com/mapping.json' @params |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also, why isn't the mappingfilePath just part of the params
JamesWTruher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems fine
tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml
Outdated
Show resolved
Hide resolved
d3c7d19 to
5251b2d
Compare
tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml
Outdated
Show resolved
Hide resolved
* Add verbose to clone * Add skip publish parameter * install the pmc cli * Address PR comments * use updated path * switch to main-mirror * Don't install python * Update tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml * Update tools/releaseBuild/azureDevOps/releasePipeline.yml
* Add verbose to clone * Add skip publish parameter * install the pmc cli * Address PR comments * use updated path * switch to main-mirror * Don't install python * Update tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml * Update tools/releaseBuild/azureDevOps/releasePipeline.yml
* Add verbose to clone * Add skip publish parameter * install the pmc cli * Address PR comments * use updated path * switch to main-mirror * Don't install python * Update tools/releaseBuild/azureDevOps/templates/release-PublishPackageMsftCom.yml * Update tools/releaseBuild/azureDevOps/releasePipeline.yml
PR Summary
Start using new packages.microsoft.com cli
PR Context
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.(which runs in a different PS Host).