Continuous Integration (CI) is a software development methodology that uses small and frequent incremental changes to the code base, which are incorporated into a rapid build and test environment. Each change integrated into the source repository is verified by the...
Continuous Integration
How Engineers Used Twitter During SolidWorks World 2018
Last week, SolidWorks held its annual conference, SolidWorks World 2018, in Los Angeles where over 5,000 engineers, manufacturers, educators and enthusiasts attended. Many who could not attend streamed the conference sessions online and scanned the 5000+ tweets that...
Continuous Integration Best Practices—Part 4
As I noted in other articles in this "Continuous Integration Best Practices" Series (click here for Part 1, Part 2, or Part 3", there are 10 best practice principles associated with Continuous Integration and in this previous articles, we covered the first eight. In...
Continuous Integration Best Practices—Part 3
As I noted in "Continuous Integration Best Practices—Part 1" and "Continuous Integration Best Practices—Part 2" there are 10 best practice principles associated with Continuous Integration and in this previous articles, we covered the first six. In this article, we...
Continuous Integration Best Practices—Part 2
As I noted in "Continuous Integration Best Practices—Part 1" there are 10 best practice principles associated with Continuous Integration and in this previous article, we looked at the first three. For part 2, we pick up where we left off and talk about principles...
Continuous Integration Best Practices—Part 1
Continuous Integration is a leading software development methodology whereby new development is constantly being submitted and tested against the main body of work. The goal being rapid feedback on incremental changes, resulting in lower maintenance costs and higher...
The Difference Between Continuous Delivery and Continuous Deployment
In my previous article, I define and compare the two software development practices of Continuous Integration and Continuous Delivery. The two practices are complementary and potentially overlapping, but at least their names give us the hint that they are distinct. If...
Continuous Integration Best Practice: Including a Version Number in Builds
Building software source code is an integral part of continuous integration and is the backbone of developing useful software. By “build”, I mean that the source code needs to be received as input to a compiler and a binary of some sort emitted for the software to...
5 Continuous Integration Best Practices to Consider
This week we would like to have a look at some continuous integration best practices. The list presented here is not exhaustive, and was inspired by a larger post on the topic at: http://www.thoughtworks.com/continuous-integration Our purpose is to expand on some of...
Continuous Integration in 8 Easy Steps with Buildbot
Several weeks ago, Ron provided some great insight regarding how to install the Hudson continuous integration tool on Windows. This week, I'll be discussing a different tool: Buildbot. My initial exposure to continuous integration tools in general was only a few years...
How to Install the Hudson Continuous Integration Tool on Windows
This week we are going to begin taking a look at Hudson, a widely used continuous build and integration tool. Hudson is a state of the art continuous build tool which now has seen wide adoption for software engineering. Hudson supports most of the more prominent...
ElectricCommander Custom Dashboards: How to Visualize Your Build Data
Whenever I get a chance to see any kind of motor racing I am amazed at how many displays the engineers use to watch and monitor all the data coming from the cars. Modern performance racing cars produce a lot of data about the engine, tires, fuel consumption,...