jenkins continuous integration cookbook

This article refers to the following:http://my.oschina.net/uboluo/blog/157483Http://java.dzone.com/articles/automating-continuousPreviously, the APK was manually generated via the IDE (Eclipse or Android Studio) and sent to testers via QQ or email, and now the Division requires continuous integration of the project, that is, in some way timed (e.g. three o'clock in the morning per night) Automatically pull

SH script to the remote server and execute the script (the script is mainly to close Tomcat and delete the war package under WebApps)//SCP sshexec4. Copy the war package to the remote server5. Launch Tomcat, deploy complete.The sh script, which is used to close Tomcat and delete the war package, uses the way to kill the process instead of the Tomcat-shutdown script, because when Tomcat is closed, execution shutdown.sh will error:#!/bin/bash#KillTomcat Piduser=`WhoAmI' Pidlist=`PS-ef|grepapache-

variable is in effect, enter on the command line: Git version will show git versions, such as:Five, git install directory configurationEnter the system Management-Global Tools Configuration page in Jenkins to add the following configuration, such as:Vi.. Project configurationWhen set up, there will be no error, such as:After saving, start building, such as:The build succeeds, but the execution fails, and the build steps need to be added, such as:Afte

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 spec

------------------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

Use of the system is Ubuntu, so there are a lot of apt-get commands, haha forgive Install git Git-core Create a new Git user, and the user's home directory will be used to store git Repository. This user name is not necessarily called git, can be arbitrarily specified, but git is more commonly used, a look at the role of this account Modify the password Landing sudo install git git-coreadduser gitpasswd gitsu gitThe above is a git installation Get Gitolite

File (Web project Direct input solution name, for example)Command Line Arguments (the first row in the build parameter is to rebuild the solution; The second line is to build the release version; the third line is to build the 4.0 version of Framwork)At this point, the project code of the Automatic acquisition, compilation has been configured to complete, the next is the deployment of the problem, study the FTP plugin does not solve the problem, I am currently using the Hudson Post build taskBe

1. Install the pipeline plug-in and first recognize 1. Start Jenkins, open browser http://localhost:8080, system administration, user name: chenshanju/123456 2. System Management-plug-in management, install pipeline plugin 3. Configuring the MAVEN EnvironmentSystem Management-Global tool configuration.If MAVEN is not installed on this machine and the name is set to M3, select Install MavenIf MAVEN is installed on this machine, the nam

8. Check code updates and compileYou can set the timer check compile function by poll SCM.For example, */5 * * * * is checked every 5 minutes, if there is an update in the Git repository, the build operation is performed.9. Speed up download with mavenSee: http://blog.csdn.net/sheismylife/article/details/7209722Jenkins '. M2 directory path in:/var/lib/jenkins/.m2/Clear all Jar packages First, then create the settings.xml file and edit the following:No

Jenkins integration-Where are styles ?, Jenkins integration-style 1. Blog background Jenkins continuous integration, along the way the ups and downs continue, but from every ups and do

= "Run tools in parallel" >description= "Prepare for Build" >description= "Find coding standard violations using Php_codesniffer creating a log file for the continuous integration serv ER ">============end===============Configuration of the PHPUnit============phpunit.xml=========================end=================Enter Jenkins's task directory, typically in:/var/lib/je