Skip to content
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

Merged
merged 9 commits into from
Feb 5, 2024
Merged

build: Support 1ES pipelines #1685

merged 9 commits into from
Feb 5, 2024

Conversation

bwateratmsft
Copy link
Contributor

No description provided.

@bwateratmsft bwateratmsft requested a review from a team as a code owner February 2, 2024 19:17
@@ -0,0 +1,17 @@
steps:
- task: Npm@1
displayName: "\U0001F449 Package"
Copy link
Contributor Author

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
Copy link
Contributor Author

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

Copy link
Member

@MRayermannMSFT MRayermannMSFT left a 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. 🙈

@bwateratmsft bwateratmsft merged commit bb6c454 into main Feb 5, 2024
4 checks passed
@bwateratmsft bwateratmsft deleted the bmw/1es branch February 5, 2024 14:30
@nturinski
Copy link
Member

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?

@bwateratmsft
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants