Currently Travis does the CI, but I would like to use the VSTS release system to create the full packages, similar to what I did with gui.cs and include the native payloads on each package and remove the manual steps currently in the packaging.
Tasks:
[x] Build on VSTS
[x] Setup PR builds on VSTS
[x] Set package name based on branch name
[x] Trigger release pipeline based on branch names, and publish to NuGet
[ ] Create an environment that can install the generated package (regardless of the pre labels).
[ ] Alter the csproj files so that they can use based on an environment variable a package, rather than referencing a local csproj, so we can use the nuget from the drop
[ ] Run tests from installed package on Mac
[ ] Run tests from installed package on Windows
[ ] Run tests from installed package on Linux
[ ] For releases, validate that the csproj project name matches the branch name, or fail otherwise
Currently Travis does the CI, but I would like to use the VSTS release system to create the full packages, similar to what I did with gui.cs and include the native payloads on each package and remove the manual steps currently in the packaging.
Tasks: