My Experience Writing a Build System. Lately there’s been some interest in build processes among various people — Vellum was announced a while back, Ben has been looking for a tool and looking at Fabric, and Kevin announced Paver.
At the same time zc.buildout is starting to gain some users outside of the Zope world, and I noticed Minitage as an abstraction on top of zc.buildout. A while ago I started working on a build project for Open Plans called fassembler. 10 Ideas For Web of Data Apps. At the end of last week, we posted an open thread asking what application you'd build (or would like someone else to build) using linked data or open data.
The thread was inspired by Georgi Kobilarov. In this post, we list 10 of the best ideas we received. A number of the suggested apps were for social good, for example apps for improving sustainability and finding missing persons. Other apps were more lifestyle-oriented, for example for cooking and genealogy. A few were business focused, such as a brand marketing app and a point-of-sale system. Scott Sims » Blog Archive » Configure the Team City rake runner to launch Selenium Grid tests. This article will describe how I was able to use the team city rake runner to launch selenium grid tests.
I learned a few tricks to get this to work correctly. I first had to learn the makeup of a rspec specktask. Next I needed to understand how to pass in spec options and lastly I needed to write a rake task that would execute in an exact order. I needed to still generate the html report with the rake task so I had to add the formatter path to the rake runner Setup the report formatter path in your rake runner like you do in your rake file.See the code below to see how the formatter path is setup in the rake file. Setup the spec opts in the rake runner. How We Do It: Building the Visual Studio Product Line.
Where To Now with Build Automation? Most developers nowadays are familiar with the basic tenets of Continuous Integration, but arguably only a small proportion of these are fully benefiting from an optimized CI set up.
Indeed, an effective Continuous Integration environment can save your team time, money and even existential angst. It can enable bugs to be discovered earlier, their cause identified more easily, and ultimately get them resolved more efficiently. It can encourage better source code management practices, help you leverage automated analysis tools, encourage better testing, track your progress and remove bottlenecks from your developers lives.
Why is continuous integration hard? - Distilled Brilliance. Getting a good continuous integration process in place poses many challenges. One of the biggest is making sure you have the discipline to support it. Preaching to the choir I recently attended a talk by Eric Pugh of Open Source Connections on the fundamentals of , or CI for short. I'm certainly no stranger to CI practices, so this was a case of preaching to the choir for me, although it's obviously nice to hear things that you already believe validated by others who are respected in the field. On the surface, it might not seem very useful to go to a talk where you already agree with most of what the speaker's going to say, but in fact, there's a good amount of value. As Eric zipped through his slides with practiced ease, I couldn't help watching some of the facial reactions of the attendees.
So what's so hard about CI? Initially, it may not seem like CI should be hard, and that its benefits should tend to outweigh its costs anyway. Practice is the easy part; discipline is the challenge. Continuous Integration Strategies (Part II) DamageControl - Continuous Integration Server Feature Matrix. CI Factory - getting it working with your development tools in D:\Program Files. Jitterbit Open Source Integration - Business Integration Made Easy. BizTalk 2006 Deployment Framework Docs. Deployment Framework for BizTalk 2006 - Core Tools & Sample Application (Document version 1.0)
RSBuild SQL Server Reporting Service Deployment Tool. Fear and Loathing : Simple NAnt integration with Visual Studio. Generally I use the most excellent TestDriven.NET for my building in Visual Studio as it can run tests and identify failed tests (with a context to jump to the error).
Often though I have a setup (usually with a client) where they don't have the ability to run this addin or just want to build their systems and don't have unit tests (yes, it does happen, oh horrors of horrors). Also TestDriven.NET won't build an entire system and do additional stuff like maybe copying files for deployment, running database scripts for agile database development, etc. so you look to something more complete to automate the process. The key thing about building systems when you have multiple team members is to have everyone build the same thing. We want to avoid the "it works on my machine" syndrome.
This can be a problem though when someone goes off and tweaks some personal setting, or only builds part of the solution and forgets steps if the build is complicated. BizTalk Server Samples and BizTalk Forum. Donald Farmer on SQL Server Integration Services : Web Services Architect : Articles : Web Services and STP. Wednesday June 26 2002 Web Services and Straight Through Processing Web Services in the Financial Industry Gunjan Samtani and Dimple Sadhwani Printer-friendly HTML version . This article discusses the fundamentals of STP, the need for, driving forces behind, and benefits of STP, the current state of technology supporting STP, and the relationship of enterprise and business-to-business application integration and business process management with STP.