We are glad to present our seventh compilation of recent TeamCity-related articles and blog posts to you and we hope you will enjoy it. If you yourself stumble upon something interesting on the topic, or create your own piece on using TeamCity, please make sure to share it with us.
Darren Guy documents his experience setting up an automated build and deployment solution for Sitecore in a series of posts. Parts 1 and 6 focus specifically on TeamCity, other parts are linked to from each of these posts:
Building a Continuous Integration Environment for Sitecore Part 1 – Teamcity
Building a Continuous Integration Environment for Sitecore Part 6 – TeamCity project
Robert Firek from Codurance has put together this guide for creating a (somewhat simplified) continuous deployment pipeline based on Docker and TeamCity: Docker Meets Continuous Deployment.
Raygun’s Chief of Engineering describes their Continuous deployment process which lets them deploy 6 times per day. To achieve this, they use TeamCity and Octopus Deploy, among some other tools: Continuous Deployment: How To Make It Safer.
Visual Studio Team Services has released an update which can now consume TeamCity builds as artifacts in Release Management:
— Release Management (@vsreleasemgmt) May 23, 2016
These two articles describe a Rails project continuous integration environment using TeamCity and Bitbucket. A curious note: the author focuses on using the default free edition of TeamCity which provides 20 build configurations and 3 build agents:
Deploy Your Rails Continuous Integration Environment With TeamCity and BitBucket (Part I: Initial Setup)
Deploy Your Rails Continuous Integration Environment With TeamCity and Bitbucket (Part II: Rails Integration)
Read this short post if you would like to avoid deployment on weekends and configure date/time triggers defined by a CRON expression in TeamCity accordingly: Run Web Application Deployment in TeamCity – Only on Weekdays.
See all TeamCity Digests.