CNUG Showdown: Continuous Integration and Deployment tools - AppVeyor
•Download as PPTX, PDF•
0 likes•108 views
This is the slides presented at the CNUG meetup "Showdown: Continuous Integration and Deployment tools" regarding AppVeyor.
Recommended
More Related Content
Similar to CNUG Showdown: Continuous Integration and Deployment tools - AppVeyor
Similar to CNUG Showdown: Continuous Integration and Deployment tools - AppVeyor (20)
Recently uploaded
Recently uploaded (20)
CNUG Showdown: Continuous Integration and Deployment tools - AppVeyor
- 1. Short presentation by Kim Christensen and Christian Mikkelsen
- 2. ABOUT US Former colleagues at Telenor MVNO, where we worked with TeamCity and AppVeyor. Kim Christensen, SimCorp Christian Mikkelsen, Telenor MVNO
- 3. AGENDA Configuration Extensibility What is AppVeyor? Builds Tests Artifacts Deployment Notifications Pros and cons
- 4. WHAT IS APPVEYOR? A cloud service providing ◦ Continuous Integration ◦ Continuous Deployment
- 5. PLANS ◦ Free for open source ◦ Basic (29$) ◦ Professional (59$) ◦ Premium (99$) ◦ Enterprise (on premise)
- 6. PHOENIX SERVERS (Martin Fowler)
- 7. GET STARTED Connect to your favorite VCS Select your repository You are ready to start working
- 8. FIRST COMMIT Make your first push Watch the build kick off
- 9. Enjoy the feedback in your VCS
- 10. CONFIGURATION How to configure the build
- 11. APPVEYOR INTERFACE Through the AppVeyor interface
- 12. YAML Through an YAML file
- 13. WHY USE THE YAML FILE? Version controlled Access to interface not required Developer empowerment! Configuration can be changed per build and are explicit
- 14. MINIMUM YAML
- 15. BUILD WORKER IMAGES Consists of ◦ A template ◦ Preinstalled software
- 16. CUSTOMIZATION OF IMAGES Images can be “customized” using ◦ PowerShell ◦ Chocolatey ◦ WebPI (Microsoft Web Platform)
- 17. SERVICES Popular services are pre installed ◦ Databases ◦ Internet Information Services ◦ Microsoft Message Queuing
- 18. BUILDS How to run a build
- 19. SIMPLE BUILDS Consists of 1 job Rolling Can be started automatically on push Can be scheduled Solution file autodiscovering
- 20. BUILD MATRIX Consists of multiple jobs Different platforms and configuration Failing strategies
- 21. BUILD CACHING Preserve files across builds Cache size defined by account Removal is manual
- 23. RUNNING TESTS Autodiscovery Specific assemblies Custom test scripts
- 24. PARALLEL TESTS Based on build matrices Split tests across VMs Test categories Environment variables
- 28. EXAMPLE YML
- 33. EXTENSIBILITY Ways to extend AppVeyor
- 35. ◦ No setup ◦ No maintenance ◦ Phoenix servers ◦ Version control ◦ YAML PROS AND CONS ◦ Cloud dependent ◦ Debugging ◦ Windows specific ◦ Documentation Pros Cons
Editor's Notes
- Not gonna talk much about deployment
- Site hosted on Azure Build agents hosted on RackSpace and Google Cloud Not gonna talk much about deployment
- Private repositories only on paid versions Plan != pricing ?
- Clean vm images, which are preheated Vm images hosting build agents No state perserved (dll’s, installs, user configs etc) Data dies on exit This will make your dependencies more visible and repository selfcontained Custom images can be supplied As a new developer would check out
- Sync’s user teams to some degree
- Every build runs on a new VM, Phoenix Server
- Every build runs on a new VM, Phoenix Server
- In darkness bind them Like most other CI products This binds your setup to the product Requires backup etc
- Inspired by TravisCI Resides in your repo making the repo selfcontained Maybe something with secrets
- Version controlled - No backup required, explicit CI dependencies and kept at a minimum, easy to transfer to other CI since it is human readable which means easy to setup in eg TC, minimum cut + maximum flexibility, overview easy Access to interface not required - Means faster setup, developer can handle it Developer empowerment - can understand and change it, up an run in minutes instead of hours/days
- Inspired by TravisCI Almost everything we talk about in the following can be configured in the YAML file Minimum will, build and run tests
- Template: Visual Studio 2013, 2015 (Windows Server 2012 R2) and 2017 (Windows Server 2016) Preinstalled Version Control: Git, Mercurial, Subversion Visual Studio in different versions Langauges: Go, Java, Node.js, Ruby, Python, Perl, Erlang, TypeScript, C++, C And many more, read documentation
- Custom images is possible, but not generally available If you can “install” it, you can use it. You have admin rights.
- Preinstalled but disabled SQL Server Express with Advanced Services (full install, Reporting Services, Replication, Full-Text Search) 2008, 2012, 2014, 2016 MySQL PostgreSQL MongoDB
- Rolling: Only chooses the newest checkin in a revision or PR
- Dimensions is: Operating system, environment variables, platform (x64, x86, Any CPU), configuration (Build, Debug), test categories Different services also possible Failing strategies: Fast finish, allow failures
- Fx. NuGet, NPM, Ruby Gems, Large files, Chocolatey dependencies Cache dependencies defined in YML Cache validation rules can be written
- Auto discovery, searches recursively for MSTest, NUnit, xUnit.net and MSpec tests
- Test categories can be used in available, otherwise environment variables can be used
- And more, AzureCloudService, AzureCloudServiceConfig, SsdtPackage (dacpac) Default pushed to AppVeyor nuget feed if nuget package
- Symbol sources not pushed by default Feed can be accessed by builds if wanted. Good for internal dependencies.
- FTP/SFTP WebDeploy SQL (SSDT) AWS Azure GitHub Bintray Deploy on tag
- Email: Project and global Chats: Slack, HipChat, Campfire, VSO Team Rooms Messages can be customized Also tray support using Catlight
- No setup - no install, no hw, no ad users, etc, No maintenance - maybe except images if custom or not default YAML - The simplicity, no special skills required, every developer can adapt