InfoQ Homepage Continuous Integration Content on InfoQ

Articles

RSS Feed

Newer Older

Codenvy’s Architecture, Part 1

Tyler Jewell, CEO of Codenvy, unveils in this 2-parts article the architecture of Codenvy - a cloud IDE –, providing details on its platform and plug-in architecture, workspace and cluster management, multi-tenancy implementation, IDE collaboration, release model and SCRUM process used for development.

Tyler Jewell
on Sep 27, 2013
The Technology behind Codenvy. An Interview with Tyler Jewell, CEO

Codenvy is an online IDE supporting applications development in Java, JavaScript, HTML5, PHP, Ruby and other languages, with built-in support for deploying the apps on a PaaS. This article includes an interview with Tyler Jewell, CEO, detailing some of the technologies behind Codenvy.

Abel Avram
on Jul 07, 2013
Managing Build Jobs for Continuous Delivery

The number of jobs in a continuous integration tool can range from a few to several thousand, all performing various functions. There is an approach to manage these jobs in a more efficient manner.

Martin Peston
on May 24, 2013
Automated Builds: How to Get Started

The first part of this series discussed some of the benefits of automating your build and deployment processes. In this article, we will take a common example of a corporate web application for a fictional financial institution, and walk through fully automating their build process.

Joe Enos
on Feb 04, 2013
Automated Builds: The Key to Consistency

If there's one thing software developers are good at, it's automating things that used to be done manually. Making life easier for everyone by letting computers handle tedious repeatable tasks, allowing people to focus on what matters to them is what we’re here for. However, development teams often neglect the one audience that would benefit the most - themselves.

Joe Enos
on Jan 02, 2013
Continuous Integration with MSBuild and Jenkins – Part 2

In part one we looked at using MSBuild in a general sense. Part 2 we apply that knowledge to a specific continuous integration server, namely Jenkins. We choose Jenkins because it is an open source project that supports a wide variety of projects, making it ideal for heterogeneous environments.

Mustafa Saeed Haji Ali
on Oct 01, 2012
Continuous Integration with MSBuild and Jenkins – Part 1

In this first of a two-part series, Mustafa Saeed Haji Ali looks at implementing a continuous integration system using MSBuild. Part two will how to integrate this into Jenkins, an extendable continuous integration server with support for a wide variety of operating systems and programming languages.

Mustafa Saeed Haji Ali
on Sep 20, 2012
Lessons From A DevOps Journey

Matt Callanan has been pushing the boundaries of Agile software development for over six years and most recently he extended that journey to DevOps. He recently shared his experiences in a talk at the Agile Development Practices West conference entitled "Lessons From A DevOps Journey". InfoQ caught up with Matt prior to the conference to find out more about his experiences in DevOps.

Craig Smith
on Jun 27, 2012
Thoughts on Test Automation in Agile

Rajneesh Namta shares the lessons he’s learned while automating software tests on a recent Agile project. The techniques he recommends illustrate how the Agile principles we follow when building software apply equally as well to building an automated regression test suite: start small, build iteratively and incrementally, prioritize, focus on value, work transparently, respond quickly to change.

Rajneesh Namta
on Feb 21, 2012
Test automation and Continuous Delivery

This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing.

Ranjan D Sakalley
on Oct 21, 2011
Patterns for Continuous Delivery

There is no one-size-fits-all solution to implementing Continuous Delivery. The number and composition of the teams will greatly affect what options are available and what trade-offs need to be made. Staff editor Jonathan Allen reflects on some of the patterns he has observed over the last 15 years.

Jonathan Allen
on Sep 15, 2011
Skills for Scrum Agile Teams

The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.

Prasad Prabhakaran
on Jul 26, 2010

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Login with:

Don't have an InfoQ account?

Articles