|By Cynthia Dunlop||
|May 30, 2013 04:01 PM EDT||
Build automation is undeniably a critical component of Continuous Integration. But in the most creative and advanced companies, Continuous Integration extends far beyond build automation, enabling them to achieve greater scalability, productivity, and quality throughout the SDLC.
Here are 6 steps to taking your Development Testing activities (and more) from manual integration to Continuous Integration—in less than a day.
1. Identify Manual Processes
Start off by taking an inventory of your regular time-consuming efforts. Your goal is to identify tedious “must do” tasks that you or your team performs over and over. The processes you identify may include:
- Transferring files between machines
- Entering commands in a console
- Copying data between different systems or into another format
- Visually verifying information, data, or test results
- Writing documentation
- Getting verbal or written approval
- Scheduling and participating in meetings
- Clicking a button/icon to execute a script or program
- Creating and sending reports
At this stage, you don't need to worry about automation; focus on determining tedious, routine manual processes. If creating this list takes longer than 15 minutes, stop where you are and move to step two.
2. Estimate Frequency and Duration
Now that you've created a short list of these processes, your next step is to determine the relative gains from automation. The easiest way to do this is by estimating frequency and duration. When estimating the frequency of a process, don't limit yourself to current conditions. Instead, focus on the value of the process by considering how often you would use the results or how long it takes before the results become outdated:
- Several times per day
- A few times per week
- Every sprint
- Twice per release cycle
Next, go through the list and estimate how long it takes to complete each process under current conditions. Durations can range from minutes to days for common process. It’s a natural human tendency to underestimate durations, so feel free to round up or add fudge factors.
3. Select (Sub) Processes for Automation
Review your list and choose one item that if automated would noticeably improve your software development team’s productivity. Common selection methods include:
- Choose the process with the highest duration
- Choose the process with the highest frequency
- Choose the process with the highest (frequency) * (duration)
At this point, many people make the mistake of taking an “all or nothing” view. Instead, focus on the portions of the process that can be automated and proceed with the understanding that you will improve as you go.
Go through the exercise of doing the task, either mentally or physically, and make notes for each step. Jot down information gathered, commands entered, permissions needed, people involved, etc. – enough to jog your memory later.
The end result will be a mini instruction manual for a repeatable human process. Review your instructions and identify the steps that a computer can perform. Commands you entered into a console or textbox and any information pulled from a website or database are good candidates. For multi-person and multi-stage processes, also pay attention to methods of notifying individuals of their turn and role in the process
4. Create Automation Scripts
Look through your instruction manual from the last step, then:
- Copy your console commands into an editor and save them as .bat (Windows) or .sh (Unix/Linux) scripts
- Use a development testing tool with a command line interface to
- Statically analyze code for safety, security, and defects
- Automatically generate and run unit tests
- Automatically assign and track peer review tasks
- Functionally test APIs
- Scrape websites, services, and databases for intermediate data
- Use build and reporting tools to inform subsequent stages of the automation infrastructure
- Capture multi-stage processes in the form of BPEL or another high-level process engine
The goal is to keep it simple and target the low-hanging fruit—you can worry about optimization, generalization, and parameterization later.
5. Schedule and/or Trigger the Artifacts
The formally-accepted definition of continuous integration specifies that your script must be triggered by a commit to your SCM. Most people, however, really just care about getting work done. Whether their processes match one definition or another is beside the point. Feel free to carve out your own interpretation of CI that saves you the hassle of tedious tasks.
Now that you have a script or other automatable artifact, you need a tool to manage the scheduling/triggering of those artifacts. One straightforward strategy for finding automation tools is to search for the term continuous integration; the results will yield tips on automating not just the build, but scores of other development, QA, and IT activities. CI tools provide the simple and necessary framework for scheduling the regular runs of some artifacts and stitching together the triggered runs of others.
6. Iterate, Improve, Repeat
With the time you saved automating your Development Testing processes, you can now focus on improving your basic continuous integration implementation. Go back to step one and add some new manual tasks to your list. For example, maybe you manually modify certain scripts or copy them for slightly similar purposes. Your next automation project might be to consolidate and parameterize your automation artifacts
You just jumped 2-3 CMMI levels (for those keeping score). Congrats!
Electric power utilities face relentless pressure on their financial performance, and reducing distribution grid losses is one of the last untapped opportunities to meet their business goals. Combining IoT-enabled sensors and cloud-based data analytics, utilities now are able to find, quantify and reduce losses faster – and with a smaller IT footprint. Solutions exist using Internet-enabled sensors deployed temporarily at strategic locations within the distribution grid to measure actual line loads.
Oct. 9, 2015 03:49 PM EDT
You have your devices and your data, but what about the rest of your Internet of Things story? Two popular classes of technologies that nicely handle the Big Data analytics for Internet of Things are Apache Hadoop and NoSQL. Hadoop is designed for parallelizing analytical work across many servers and is ideal for the massive data volumes you create with IoT devices. NoSQL databases such as Apache HBase are ideal for storing and retrieving IoT data as “time series data.”
Oct. 9, 2015 03:45 PM EDT Reads: 503
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome,” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Oct. 9, 2015 03:45 PM EDT Reads: 137
Today air travel is a minefield of delays, hassles and customer disappointment. Airlines struggle to revitalize the experience. GE and M2Mi will demonstrate practical examples of how IoT solutions are helping airlines bring back personalization, reduce trip time and improve reliability. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Dr. Sarah Cooper, M2Mi's VP Business Development and Engineering, will explore the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context w...
Oct. 9, 2015 03:30 PM EDT Reads: 104
The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, will explore the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
Oct. 9, 2015 03:05 PM EDT
The IoT market is on track to hit $7.1 trillion in 2020. The reality is that only a handful of companies are ready for this massive demand. There are a lot of barriers, paint points, traps, and hidden roadblocks. How can we deal with these issues and challenges? The paradigm has changed. Old-style ad-hoc trial-and-error ways will certainly lead you to the dead end. What is mandatory is an overarching and adaptive approach to effectively handle the rapid changes and exponential growth.
Oct. 9, 2015 03:00 PM EDT Reads: 199
Today’s connected world is moving from devices towards things, what this means is that by using increasingly low cost sensors embedded in devices we can create many new use cases. These span across use cases in cities, vehicles, home, offices, factories, retail environments, worksites, health, logistics, and health. These use cases rely on ubiquitous connectivity and generate massive amounts of data at scale. These technologies enable new business opportunities, ways to optimize and automate, along with new ways to engage with users.
Oct. 9, 2015 02:00 PM EDT Reads: 187
The buzz continues for cloud, data analytics and the Internet of Things (IoT) and their collective impact across all industries. But a new conversation is emerging - how do companies use industry disruption and technology enablers to lead in markets undergoing change, uncertainty and ambiguity? Organizations of all sizes need to evolve and transform, often under massive pressure, as industry lines blur and merge and traditional business models are assaulted and turned upside down. In this new data-driven world, marketplaces reign supreme while interoperability, APIs and applications deliver un...
Oct. 9, 2015 02:00 PM EDT Reads: 301
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
Oct. 9, 2015 02:00 PM EDT Reads: 232
The IoT is upon us, but today’s databases, built on 30-year-old math, require multiple platforms to create a single solution. Data demands of the IoT require Big Data systems that can handle ingest, transactions and analytics concurrently adapting to varied situations as they occur, with speed at scale. In his session at @ThingsExpo, Chad Jones, chief strategy officer at Deep Information Sciences, will look differently at IoT data so enterprises can fully leverage their IoT potential. He’ll share tips on how to speed up business initiatives, harness Big Data and remain one step ahead by apply...
Oct. 9, 2015 01:45 PM EDT Reads: 561
There will be 20 billion IoT devices connected to the Internet soon. What if we could control these devices with our voice, mind, or gestures? What if we could teach these devices how to talk to each other? What if these devices could learn how to interact with us (and each other) to make our lives better? What if Jarvis was real? How can I gain these super powers? In his session at 17th Cloud Expo, Chris Matthieu, co-founder and CTO of Octoblu, will show you!
Oct. 9, 2015 01:15 PM EDT
As a company adopts a DevOps approach to software development, what are key things that both the Dev and Ops side of the business must keep in mind to ensure effective continuous delivery? In his session at DevOps Summit, Mark Hydar, Head of DevOps, Ericsson TV Platforms, will share best practices and provide helpful tips for Ops teams to adopt an open line of communication with the development side of the house to ensure success between the two sides.
Oct. 9, 2015 01:00 PM EDT Reads: 601
SYS-CON Events announced today that ProfitBricks, the provider of painless cloud infrastructure, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. ProfitBricks is the IaaS provider that offers a painless cloud experience for all IT users, with no learning curve. ProfitBricks boasts flexible cloud servers and networking, an integrated Data Center Designer tool for visual control over the cloud and the best price/performance value available. ProfitBricks was named one of the coolest Clo...
Oct. 9, 2015 01:00 PM EDT Reads: 793
SYS-CON Events announced today that IBM Cloud Data Services has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. IBM Cloud Data Services offers a portfolio of integrated, best-of-breed cloud data services for developers focused on mobile computing and analytics use cases.
Oct. 9, 2015 12:00 PM EDT Reads: 738
SYS-CON Events announced today that Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, will keynote at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA.
Oct. 9, 2015 11:15 AM EDT
Developing software for the Internet of Things (IoT) comes with its own set of challenges. Security, privacy, and unified standards are a few key issues. In addition, each IoT product is comprised of at least three separate application components: the software embedded in the device, the backend big-data service, and the mobile application for the end user's controls. Each component is developed by a different team, using different technologies and practices, and deployed to a different stack/target - this makes the integration of these separate pipelines and the coordination of software upd...
Oct. 9, 2015 09:00 AM EDT Reads: 296
Mobile messaging has been a popular communication channel for more than 20 years. Finnish engineer Matti Makkonen invented the idea for SMS (Short Message Service) in 1984, making his vision a reality on December 3, 1992 by sending the first message ("Happy Christmas") from a PC to a cell phone. Since then, the technology has evolved immensely, from both a technology standpoint, and in our everyday uses for it. Originally used for person-to-person (P2P) communication, i.e., Sally sends a text message to Betty – mobile messaging now offers tremendous value to businesses for customer and empl...
Oct. 9, 2015 08:30 AM EDT Reads: 308
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
Oct. 9, 2015 07:00 AM EDT Reads: 5,884
WebRTC converts the entire network into a ubiquitous communications cloud thereby connecting anytime, anywhere through any point. In his session at WebRTC Summit,, Mark Castleman, EIR at Bell Labs and Head of Future X Labs, will discuss how the transformational nature of communications is achieved through the democratizing force of WebRTC. WebRTC is doing for voice what HTML did for web content.
Oct. 9, 2015 06:00 AM EDT Reads: 1,415
Nowadays, a large number of sensors and devices are connected to the network. Leading-edge IoT technologies integrate various types of sensor data to create a new value for several business decision scenarios. The transparent cloud is a model of a new IoT emergence service platform. Many service providers store and access various types of sensor data in order to create and find out new business values by integrating such data.
Oct. 9, 2015 04:00 AM EDT Reads: 570