Источник:
http://feedproxy.google.com/~r/Dynam...-pipeline.html
==============
The legacy pipeline from the build VM has its own PowerShell script that generates the packages. However, it always puts the F&O platform version into the package file name which can make it more difficult to use release pipelines or
including ISV licenses into your packages since the version number changes with each update, requiring you to update your pipeline settings (and finding out the actual build number to use). Continue reading below or watch the
YouTube video to learn how to swap the packaging step from the legacy pipeline with the Azure DevOps task which lets you specify your own name for the deployable package zip file. You can find the official documentation on
the packaging step here.
Read more...
Источник:
http://feedproxy.google.com/~r/Dynam...-pipeline.html