-
Notifications
You must be signed in to change notification settings - Fork 68
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
build: Support 1ES pipelines #1685
Conversation
@@ -0,0 +1,17 @@ | |||
steps: | |||
- task: Npm@1 | |||
displayName: "\U0001F449 Package" |
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.
This is the 👉 emoji. It makes it much easier to visually separate what is from our template vs. what is from 1ES templates.
customCommand: run package | ||
condition: succeeded() | ||
|
||
- task: CopyFiles@2 |
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.
1ES has a publish task built in, you just have to copy the files to the publish folder
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.
LGTM. Probably get at least one other azcode folk to review though. 🙈
So for clarification, does this mean that we'll stop publishing our @microsoft packages to npm and have to use the 1ES registry or whatever the equivalent is? |
We still plan to publish to NPM, but we have to do release through ESRP instead of via our own accounts / our own bot account. |
No description provided.