Sitecore JSS Meets TeamCity
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgSpBo8EQGFQzTTWcMuG_2ShjVdJE6BUsZL8X2nkSSRh6wbGDwsvuwnESjA0YbT6ouQkNa5Jvvt2qRDnxoUaOWohFXcxQEHxLDsxFZXgdIjBj5FlHTuwIxyo_wVbR1E1Bbig0Xv39igHCx8/s640/sitecore_meet_teamcity.jpeg)
The recent general availability release of Sitecore Omni / Sitecore JSS will usher in a new wave of applications and innovation leveraging the power of the Sitecore platform. The headless development approach using Sitecore JSS allows traditionally front-end focused development teams with extensive knowledge in React, Angular and Vue JS to build applications in a disconnected mode and later seamlessly integrate it with the Sitecore platform. Starting to use Sitecore JSS may seem simple at times (after all you can get started with just 4 commands ); however, the journey can quickly overwhelm teams steeped in traditional ASP.NET MVC Sitecore development. Teams are introduced to new programming languages, front-end frameworks, development tools, and build and deployment processes. In this blog, I will walk through a sample build and deployment process for a React JS Sitecore JSS application using TeamCity to deploy to an Azure PaaS Sitecore environment (XM single). Before I jump