-
Notifications
You must be signed in to change notification settings - Fork 185
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
Improve diagnostic output + refactor handling of packages-to-be-published directory in archetype-sdk-tool-dotnet.yml
#5007
Conversation
archetype-sdk-tool-dotnet.yml
archetype-sdk-tool-dotnet.yml
archetype-sdk-tool-dotnet.yml
archetype-sdk-tool-dotnet.yml
archetype-sdk-tool-dotnet.yml
archetype-sdk-tool-dotnet.yml
archetype-sdk-tool-dotnet.yml
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.
Thank you @konrad-jamrozik !
/check-enforcer override |
} | ||
displayName: Create directory for packages to publish if absent | ||
displayName: Create XOR list contents of directory of packages to publish |
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.
XOR -> or?
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 PR addresses following comment:
3.1.405
to6.x
+ assorted changes #4916 (comment)Changes made
$(Build.ArtifactStagingDirectory)/packages
;$(Build.ArtifactStagingDirectory)/packages
;Create destination directory
task, coming from produce-net-standalone-packs.yml, as it was too vague and misleading.Testing done
Tested by making a build from this PR branch and observing it behaved correctly: