In Part 1 of this 2 part tutorial series on integrating Xamarin into a continuous build environment, I detailed how to use Jenkins to build Xamarin.iOS and Xamarin.Android projects and a Team Foundation Build server to build Windows Phone Projects. In Part 2, I’ll detail how you can take advantage of Microsoft’s new Build.vNext technology that is a part of Visual Studio Online (VSO) and Team Foundation Server (TFS) 2015.
Setting Up A Continuous Build Environment For Xamarin: Part 1 - Jenkins
Continuous integration is the core foundation of the DevOps lifecycle, as it allows tests to be run and builds to be created every time a member of the development team checks in new code. This allows the team to quickly know if the latest changes have ‘broken the build’ and depending on how the continuous integration is configured, for that check in or commit to be rejected (essentially allowing the team to pre-emptively avoid major issues from ever making it into the build).