continuous integration and continuous delivery tools

Http://www.infoq.com/cn/articles/MSBuild-2Author Mustafa Saeed Haji Ali, translator Jian Li released on October 23, 2012 | Note: Swing the sleeves, take away full of dry goods, focus on the activities of the camp, from time to time hair benefits yo! 3 Discussions Share to: Weibo facebooktwitter Youdao Cloud Note email sharing Read later My list of reading This is the bottom half of the Continuous

The connection and difference between building and Continuous Integration on a daily basis 1) Continuous Integration (Continuous Integration) emphasizes a fast feedback. For example, when I check in the code, I immediately integra

are developing based On Ruby On Rails, you may choose Migration and Rake. Based on. Net, I tested Red Gate ($), Migration. Net, Machine. Migrations, Power Tools, and so on. Finally, I chose Liquibase. How to integrate it into my development process? I select the command line and command line-based MsBuild task.Use the command line to create a bat file and execute Liquibase to deploy the user database (see deploy. bat in my example ).Msbuild provides

Building continuous integration first of all to understand what is continuous integration, with a clear goal to build a continuous integration environment in order to let us go a lot less detours.

First, the continuous integration of the steps:1, continuous compilation 2, continuous database integration 3, continuous testing 4, continuous review 5,

-tier deploys.TestContinuous integration and delivery for a long time have been associated with automated testing to some extent. This groundbreaking article at Martin Fowler and Steve McConnell's early practice descriptions of daily builds and smoke tests were confirmed. In fact, this is primarily what we want to provide feedback on quality issues very quickly when performing regular build and deployment.

, dialogs, and images, where the most important product operation process meets the requirements. For UI testing, there are typically two choices: One is to use this app in a real machine or simulator, to walk through all of the app's processes, every page, and try out ways to find out if the app has an unusual performance that doesn't meet the product requirements and design drafts, based on product requirements, design drafts, and test cases. The second is to use UI Automation test

This article has been published in the "continuous integration" column on the infoq Chinese site. For more articles and video resources on "continuous integration" and "continuous delivery", visit "

Jenkins + Maven + Tomcat + SVN + Apache continuous integration Jenkins + Maven + Tomcat + SVN + Apache continuous integration construction I. Preface 1. Jenkins Jenkins version book http://mirrors.jenkins-ci.org/ 1.1 Jenkins continuous i