continuous integration and continuous delivery ppt

What is Teamcity teamcity is a powerful continuous integration (Continue integration) tool developed by JetBrains, including server side and client, currently supported by Java. NET project development. Teamcity provides a range of features that enable teams to quickly implement continuous inheritance: IDE tool

Continuous integration. NET Handbook First, the concept Martin Fowler's article: Continuous integration Chinese translation: continuous integration Second, tools Traditional tools: Visualstudio.net,visualsourcesafe,rational Clear

About JenkinsJenkins is an open source software project designed to provide an open and easy-to-use software platform that makes continuous software integration possible.Jenkins is a continuous integration tool based on Java development that monitors ongoing duplication of work, including:1.

General steps to build a MAVEN Web project using Jenkins 1 jekins from SVN pull replacement code 2 Deploying the project to the Tomcat container using Apache Tomcat Maven Plugin Specific configuration Procedures 1 New Task Enter an item name, select "Build a free-style software project", click OK2 Configuring source Management Select Subversion in source management and fill in the SVN address to build MAVEN Web project3 Configuration Build In the build, click Add Build Step and select ' Invoke

System settings are primarily used to configure some global settings paths, such as1 JDK2 Ant3 Maven4 Mailetc....Click "System Management" in the Jenkins left menu and click "System Settings" on the System administration page to enter the system settings.1 JDKClick on the "JDK" Install buttonUncheck "Auto Install"Fill in aliases and java_home2 AntSimilar JDK configuration3 MavenSimilar JDK configurationNote1 with MAVEN configuration You can also specify the location of the Setting.xml4 MailSet

In fact, the installation of this teamcity is very simple, but in the Internet to find a lot, no one to write about this aspect of the installation, Daniel do not spray, I want to use this simple little article to help more novice on the roadThe teamcity path downloaded in this article is/usr/local/src/# cd/usr/local/src/teamcity#./bin/teamcity-server.sh StartShown below:Using catalina_base:/usr/local/src/teamcityUsing Catalina_home:/usr/local/src/teamcityUsing Catalina_tmpdir:/usr/local/src/tea

------------------Build------------------------docker-compose -f ./docker-compose.ci.build.yml -p dockercompose4255153253317384266 up --buildecho ---------------Publishing...------------------docker-compose -f "./docker-compose.yml" -f "./docker-compose.override.yml" -p dockercompose4255153253317384266 up -d --buildThe app is saved and returned to the project interface. Click Build now to deploy your workWe can view the console output:Reference article:Http://www.cnblogs.com/LongJiangXie/p/751

④:gitlab of continuous integration triggers Jenkins build project One: The goal is in the company's test environment once the development to the Gitlab warehouse to submit a successful code, Gitlab notify Jenkins to build projects, code quality testing and then deployed to the test environment, note that this is a test environment, and production environment still need to manually deploy code: 1.1:jenkins c

In a previous post, someone asked why the interface test was first in line. The reason is very simple, the interface is first, the interface is not good, the subsequent coding work is limited, not to get data. Traditional interface Test interface Automatic test interface Automation Continuous integration discussion of traditional interface testing Do not know how the other people's home interface test is do