Jenkins deployment. net automated building, jenkins deployment. net

Jenkins deployment. net automated building, jenkins deployment. net

1. Environment deployment:

Windows server 2008R2 Environment 2. Related SoftwareSVN (Source Code Manager: jenkins downloads code from the source code Manager through the plug-in) Jenkins (main character) Address: JDK 1.7 or above. netframework 4.0, etc. It is best to install visual studio software 3. Install Jenkins1. Double-click the service to confirm the installation. After jenkins is installed, go to Administrative Tools> services with services corresponding to jenkins, and start the service (pay attention to permissions and port restrictions). Note: by default, jenkins is installed in the system service. However, if port 8080 is occupied, you must manually start the service. That is to say, the system cannot be started. Cmd.exe and enter the command: cd C: \ Program Files (x86) \ Jenkins (installation path) java-jar jenkins. war -- ajp13Port =-1 -- httpPort = 8899 you can start the service through port 8899. 4. Open the application in a browserAfter the service is started, go to the corresponding page through the browser: http: // ip: 8899. 1) enter the corresponding password when opening the page. A prompt is displayed on the password path. In the installation path (default main directory) secret. key; Note: The main directory contains all the information used by the current jenkins (including the source code download is placed under the main directory). If the main directory is modified, the installation is required again, all plug-ins need to be re-installed, and all the configurations have been completed, so pay attention to the placement of the home directory. Of course, you can copy the configuration to the new home directory, make sure to copy the file before deleting it. Otherwise, you need to modify the configuration. 2) The first time you open the plug-in, you need to wait for the installation of the plug-in. The installation process lasts for a long time. If the installation fails and the last update fails, the installation still fails, refresh the page and you can directly go to the system to install it. 3) log on and install the Plug-in after logging on. Go to System Management> Manage Plug-in and enter MSBuild Plugin and Subversion Plug-in on the right to find the desired Plug-in, then install. If the above preparations are all OK, the configuration will start: 5. Create a project1) Click and then appear (temporarily select to build a free-style Software Project) 6. project configuration1) enter the project name. 2) set the svn Source Code Manager path. Note that when adding svn, add the account and password. 3) Currently, I want to call a trigger remotely, so select the first trigger. 4) select the one selected above for the build environment, and the timestamp is displayed after the build. 5) the build requires configuration because msbuild is used for the build. (This is important, you can search for relevant materials)/t: Build/p: Configuration = Release/p: WebProjectOutputDir = E: \ SourceCodePublish \ Mobile/p: OutputPath = E: \ SourceCodePublish \ Mobile \ bin
6) There are many steps to perform post-build operations, as shown in the following figure: click "save". 7. start to build a project. 1) Go Back To The homepage and click "2), click [build now] 3), view the build history, and add: If the build is successful all the time, you can use vs to open the project and compile it once. Then, the build is successful, some components need to be downloaded or updated, so they fail. Good luck!

From Weizhi note (Wiz)