Hi,
I think i'm missing something really basic with the new Build.Preview system... Here my "overall" comprehension of the new build system and correct me if i am wrong.
1- The agent gets the sources
2- The agent runs all the build steps (Mine are PreBuild powershell script - MSBuild - PostBuild powershell script - Run UnitTests)
3- Copy files to staging folder (if checked in build definition)
4- Copy staging files to drop folder (if checked in build definition)
OK, because the execution of a powershell is within the build steps, there seem to be no way i can execute a script using the staging folder nor the drop folder? Just like we could do with the Tfvc.Template.12.2.xaml build process with the PostDrop powershell scripts where i could launch the deployment using the Release Management REST API to deploy my product using the vNext Release Template.
My vNext Release Template contains components wich are based on a build... so i can't call the REST API within the build steps because the drop folder hasn't been created yet...
Second thing, i dont really understand the purpose of the staging folder vs the drop folder. If i check the staging folder option in the build definition but doesnt check the drop folder option, the specified content will be copied to the staging folder but the next build will overwrite it. Still because i can't execute scripts after the staging step, there is no way i can use those staging files.
If i check the drop option but not the staging option, i get an empty drop folder... Oh nice! :)
If i check both, i get a drop folder ready for deployment but not opportunity to launch some sort of scripts to use the drop...
What am i missing?