I am a big fan of continuous delivery and deployment. You might have seen me write about it a few times before. When I first bring the idea up with clients, there is hesitation. One might even call it fear. The benefits are huge, allowing you to reap the return on investment immediately, but the big question is “how”. How does an organization switch to a continuous delivery model?
For the last year or so, I’ve been living in a mostly Atlassian world: JIRA OnDemand, BitBucket, SourceTree… likely more before the year is done. Sure, I still use our on-premise TFS 2010 at work along with Visual Studio of various editions, but my ALM world has really been rocked by those gorgeous tools from Atlassian. This past Friday I should have been doing something productive (like writing a blog post) but suddenly I was captivated by the world of Visual Studio Online. Continue reading “How Visual Studio Online won me over in under 90 minutes”
For the past few years, I have not been a big fan of incremental publishing. In fact, I’ve often recommended if there was one publishing mode to never use, it was incremental publishing. I didn’t know all the facts, but the truth was that every time I tried to implement a solution with incremental publishing the content wouldn’t publish correctly.
Over time, Sitecore has been tweaking incremental publishing and making it better, and some of the issues (like handling item renames) have been fixed in 7.2. However, if you’re still on one of the other releases, there are a few tweaks you can make to enhance your incremental publishing.
Over the last few years, I’ve been trying to iteratively improve our own processes at nonlinear to deliver better Sitecore solutions and set our clients up for maintainable and sustainable ALM processes. Some of my posts on automated Sitecore deployments with TFS or TeamCity outlined some of the initial steps we took in automated deployments. Recently, we posted a brief series to help folks getting into Application Lifecycle Management:
The first new piece of content I put together on this was a slideshare introducing ALM concepts of tool and process improvements, just to get people thinking about where they are in the process and what they need to change. I also covered how to achieve this with continuous improvement model, instead of trying to do a big-bang delivery.
The second piece I wrote covers why ALM matters for Sitecore (and pretty much any web application). The post covers some of the primary benefits of ALM, as well as how to apply ALM processes during your Sitecore implementations.
The third piece, written by my colleague Mauro, highlights some tips for automated testing of Sitecore implementations, specifically with Selenium. He’s been doing some really awesome things with automated testing of Content Editor, Page Editor, and the end-user flows.
The recommended reads: