April 29, 2015
By Rajesh Gupta, Sr. Embedded Systems Engineer, Tula Technology
Here at Tula Technology, we develop fuel efficient technologies for gasoline powered automotive engines. We adopted Perforce over two years ago for source control of Dynamic Skip Fire (DSF) technology running on a coprocessor of the Engine Control Unit.
November 05, 2014by Marc Hornbeek, Senior Solutions Architect at Spirent Communications
Within an Agile and DevOps environment, Continuous Testing (CT) is the proof of successful merges and continuous integration. At MERGE 2014, the Perforce Conference, I presented our experiences and the best practices we've put in place at Spirent Communications for Continuous-Test (CT) systems. From these experiences and best practices, we have defined the eight attributes necessary for Continuous Test Systems:
June 21, 2013by Perforce
Practitioners of continuous delivery know that committing to the mainline frequently (once a day) is a best practice. Anything that discourages this practice is to be avoided.
June 04, 2013Perforce
May 21, 2013by Perforce
I was recently on vacation and getting away from it all, I paged through a Wall Street Journal while relaxing by the pool and, lo and behold, there was an article on Agile and the family, and how there is a new generation of parents using techniques from the workplace and transplanting them to their personal lives. I'm passionate about using Agile at work, but I had never truly thought of using it at home.
If you're familiar with Agile, there are a few key roles:Posted In:
March 30, 2012
Continuous integration and Agile development are two distinct but related trends in software development. Continuous integration (CI) is really about increasing transparency, but usually manifests itself as automated build and test routines. To put it very briefly, building and testing early and often is a great way to make sure that you’re actually building what you wanted to, and expose potential problems early on.