Deployment Automation with Octopus Deploy and TeamCity, Feb. 12 Webinar
You’re probably familiar with building and testing code in TeamCity, but how do you deploy the built artifacts? How do you promote your deployments between development, test, staging and production environments, while keeping the process reliable, automated and secure? Octopus Deploy can help to solve this problem, by integrating with TeamCity to push your changes out into production.
In this session, Paul will walk through the process of building, testing, packaging and deploying an ASP.NET web applications and Windows Services into different environments using Octopus Deploy and TeamCity. This free webinar will take place Tuesday, February 12th from 15:00 – 16:00 CET (Central European Time). Space is limited; please register now.
About Paul Stovell
Paul is a .NET developer and founder of Octopus Deploy, an automated release management solution for developers on the .NET stack. Paul built the product in 2011 with a goal of making repeatable, automated deployments easy. Prior to working full time on Octopus, Paul spent years as a developer, consultant and trainer focussed on WPF, ASP.NET MVC and application architecture, working in industries ranging from investment banking to health care to mining. He is a Microsoft MVP for WPF, and has spoken at many user groups, code camps and Microsoft conferences around Australia. Paul recently returned to Australia after a year of working in London.
Subscribe to Blog updates
Maximizing Efficiency: TeamCity Cloud Introduces Per-Minute macOS Build Agents
Per-minute macOS agents are now available in TeamCity Cloud! Read this blog post to learn more.
Configuration as Code for TeamCity Using Terraform
We're introducing Terraform Provider for TeamCity, an new way for configuring your CI/CD infrastructure as code.
Critical Security Issue Affecting TeamCity On-Premises (CVE-2024-23917) – Update to 2023.11.3 Now
Summary A critical security vulnerability was identified in TeamCity On-Premises (initially discovered and reported by an external security researcher on January 19, 2024). This critical security vulnerability has been assigned the CVE identifier CVE-2024-23917 and presents the weakness CWE-2…