Sitecore End to End, Part 1

Friday, May 31, 2013 @ 10:19

By: Jon Upchurch, Senior Developer

Sitecore End to End, Part 1
A look at the development workflow of a Sitecore Project from inception to production

Series by Jon Upchurch, Matt Gartman, and Josh Jenkins

Part 1: Introduction

 

Part of being a developer is to find new and better ways to solve problems, and my team has been fortunate enough to try a number of new solutions together in a way that hasn’t been combined in this way by our organization. We are in the process of working on a group of related Sitecore sites with a small team. This poses some additional challenges in keeping things synchronized between developers both for the code and for Sitecore. Also, as Sitecore 7 is released we are in the middle of the project and there are a number of features that apply directly to the upcoming phase. As a result we will be transitioning to Sitecore 7 partway through the project.

On the purely development side, the tools we’ll be covering are the following:

  1. Visual Studio 2012
  2. Mercurial
  3. Hedgehog TDS
  4. Sitecore Glass Mapper
  5. Sitecore 6.6 and Sitecore 7

For our infrastructure we’re using:

  1. Jenkins build server
    1. Development (CI) Server Build
    2. QA Server Build
  2. Amazon EC2

We’ll be covering topics in the weeks to come relating to these areas as well as anything of interest relating to our discovery process.

This will by no means be the ONLY way to approach this project – If you ask 100 developers how to accomplish something you’ll likely get 150 different answers after all!  We can only promise that it’s been what worked for us, and what we’ve used on a daily basis for the months we’ve been involved in the particular configuration.

In the articles to come we will explain why we chose the options we did and how we implemented them. More importantly, we’ll discuss how everything worked together and what our workflow was on a day to day basis as well as along our process of integration and elevation.