» tagged pages
» logout

sorted by: recent | see : popular
Content Tagged with ContinuousIntegration + integration

Hosted Continuous Integration and Developer Tools for Ruby and Rails : RunCodeRun

ontinuous Integration Done Right * Constant feedback on the health of your project * Zero config setup with GitHub integration * In private beta - sign up for an invite below * Want to see more? Browse public projects... * Here to rumble? Browse Rails Rumble projects...

ContinuousIntegration: http://del.icio.us/popular/ContinuousIntegration

CruiseControl Home

A framework for a continuous build process. It includes, but is not limited to, plugins for email notification, Ant, and various source control tools. A web interface is provided to view the details of the current and previous builds.

ContinuousIntegration: http://del.icio.us/popular/ContinuousIntegration

Meet Hudson - hudson - Hudson Wiki

What is Hudson? [Screenshot 1] Hudson monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Hudson focuses on the following two jobs: 1. Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Hudson provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity. 2. Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Hudson keeps those outputs and makes it easy for you to notice when something is wrong.

ContinuousIntegration: http://del.icio.us/popular/ContinuousIntegration

Meet Hudson - hudson - Hudson Wiki

What is Hudson? [Screenshot 1] Hudson monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Hudson focuses on the following two jobs: 1. Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Hudson provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity. 2. Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Hudson keeps those outputs and makes it easy for you to notice when something is wrong.

Hudson: http://del.icio.us/tag/hudson+continuousintegration

Meet Hudson - hudson - Hudson Wiki

What is Hudson? [Screenshot 1] Hudson monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Hudson focuses on the following two jobs: 1. Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Hudson provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity. 2. Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Hudson keeps those outputs and makes it easy for you to notice when something is wrong.

opensource: del.icio.us tag/opensource

Continuous Integration

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage.

ContinuousIntegration: http://del.icio.us/popular/ContinuousIntegration

Page 1 | Next >>