vsts - Matching pattern does not work in NuGet Packager -


i have multiple .csproj files in git source folder , subfolders. want create nuget packages of them. if understand things correctly, should add nuget packager build step , configure path csproj or nuspec file(s) pack

**\*.csproj

but no packages created when run build. way, if manually select 'csproj' file using "..." button , run build package created.

could explain why cannot use **\*.csproj matching pattern create packages projects in source directory , subdirs? there limit nesting level or something? @ least have couple csproj files on maximum nested level 4-5 counting source folder...

p.s. know there similar bug exclusion pattern not working vsts build wonder if it's related issue?

see build configuration , log of nuget packager , nuget publisher build steps d:_work\3\s folder on build server cannot find csproj files. although can see files there, example first on d:_work\3\s\source\product\components\folder1\myproj1.csproj, second on d:_work\3\s\source\product\components\folder2\myproj2.csproj, etc... enter image description here enter image description here

the level of nesting should not issue. able setup test project 3 projects @ various levels , single nuget task created nuget package of them.

here configuration used (it default configuration @ point in time). done using version 2.x of task, if using earlier version may want upgrade.

nuget pack

you can watch happening during step setting system.debug = true when queue build. after this, can log nuget pack step , should see iterating through of directories , sub-directories , flagging match. here can see found , continues pack these 3 projects.

post detailed setup , log here if still need additional assistance.

vsts output log


Comments

Popular posts from this blog

PHP and MySQL WP -

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

go - golang pprof for c library code -