-
Notifications
You must be signed in to change notification settings - Fork 23
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
Publish symbols #973
base: main
Are you sure you want to change the base?
Publish symbols #973
Conversation
Learn Build status updates of commit 2d092eb: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
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.
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.
I suggest you add documentation about the existence of the symbols and how a custmer can use it.
.azure-pipelines/ci-build.yml
Outdated
displayName: Publish Symbols | ||
inputs: | ||
SymbolsFolder: '$(Build.ArtifactStagingDirectory)' | ||
SearchPattern: '**//Microsoft.Graph.Entra.*.nupkg' |
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.
My understanding is that symbols packages are supposed to have a .snupkg suffix. Maybe that isn't a requirement.
SearchPattern: '**//Microsoft.Graph.Entra.*.nupkg' | |
SearchPattern: '**//Microsoft.Graph.Entra.*.snupkg' |
@Ndiritu Can you take a look at this? |
2d092eb
to
6cb136a
Compare
Learn Build status updates of commit 6cb136a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
6cb136a
to
db8e202
Compare
Learn Build status updates of commit db8e202: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit f767bfd: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
No description provided.