NuGet package CI and CD
- 1. NUGET PACKAGE CI&CD Yu Guan | Microsoft MVP
- 2. Meet Yu Guan | @askguanyu twitter.com/askguanyu linkedin.com/in/yuguan askguanyu.wordpress.com devlib.codeplex.com Microsoft MVP Speaker, Blogger, Hacker, Coder, Maker, Gamer Azure, IoT, Cross-platform Apps, GIS, Services
- 3. Create build definition Add build step Delete Files Visual Studio Build NuGet Packager NuGet Publisher (CD) Variables NuGet ApiKey Triggers Continuous integration (CI) Gated Check-in
- 4. Build Step – Delete Files
- 5. Build Step - Visual Studio Build
- 6. Build Step - NuGet Packager
- 7. Build Step - NuGet Publisher
- 8. Variables - NuGet ApiKey
- 9. Triggers - Continuous integration (CI)
- 10. Triggers - Gated Check-in
- 11. Build Summary
- 12. DEMO
- 13. THANK YOU!
Editor's Notes
- #11: How do I protect my Git codebase from build breaks? If your code is in a Git repo on Visual Studio Team Services or Team Foundation Server, you can create a branch policy that runs your build. See Improve code quality with branch policies. This option is not available for GitHub repos. Can I use the CI trigger with an External Git repo? No Can I chain builds so that one build triggers another? Not yet. Do I need a build agent? You need at least one agent to run your build. Get an agent. I can't select a default agent queue and I can't queue my build. How do I fix this? See Scale out and administer your build system: Manage your queues