-
Notifications
You must be signed in to change notification settings - Fork 535
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
Add bundle analysis collection and publish steps #3149
Conversation
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.
🎂 Looks good, I'm assuming you've run the pipeline and it works? ;)
|
||
- task: PublishBuildArtifacts@1 | ||
displayName: Publish Artifacts - bundle-analysis | ||
condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest')) |
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.
succeeded()
is set based on the previous task? That's cool.
displayName: Publish Artifacts - bundle-analysis | ||
condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest')) | ||
inputs: | ||
PathtoPublish: '${{ parameters.buildDirectory }}/artifacts/bundleAnalysis' |
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 a different path than used for the Docs one below, is that intentional? How did you choose this path?
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's the path to the stuff that gets published; this just happened to be where the bundle analysis stuff went. it may be better to group it all closer together? not sure it matters much though.
#2449
Add build steps to collect and publish bundle analysis to build artifacts