Support continuous integration on build machines without the SDK installed
To build service fabric applications (*.sfproj) a MS Build
.target file are required. Those files are installed by the Service Fabric SDK. This presents a challenge in continuous deployment pipelines (ours is on Team Build) where a best practice is to keep build machines in a known, clean and maintainable state.
We would like to build Service Fabric apps in Team Build, but we don't want to install a specific version of the Service Fabric SDK onto those machines.
One solution could be to package the service fabric build artifacts as a nuget package, and then have
*.sfproj files use the props/targets from the nuget package. That way, we could restore the package in our pre-build step and happily compile our service fabric applications in VSTS without polluting the build machines.
Brian Nors Jensen commented
Is there an ETA for this?
Or at least support on hosted pools on Team Service?
Jordan Schiller commented
For continuous integration deployment it would also be nice to not have to install the SDK on a specific VM to host the builds and releases and instead be able to just use the automatically hosted VMs to build and release our service fabric apps.