hudson--Plug-in management

Hudson's use of the basic embodied in its many and powerful plug-ins, in the "System management" can be found in "plug-in management."

Hudson default comes with the following plug-ins, you can see in "Installed":

Hudson CVS Plug-in

Maven 2 Project Plugin

Hudson SSH Slaves Plugin

Subversion Plugin

The above 4 plug-ins, to see the literal meaning can be understood, respectively, to provide support for different tools.

In order to better use the Hudson, you also need to install some plugins in the "optional plug-in" to choose:

Deploy to Container Plugin: Use it for War package deployment, support Tomcat,jboss,glassfish

Hudson SCP Publisher Plugin: If you want to deploy across servers, you need to install the plug-in, which uses SCP to copy files from one server to another

Hudson Email Extension Plugin: If you want the results to be notified by mail when the deployment is complete, you can install the plugin

I only installed as above 3 plug-ins, feel that the basic functions are sufficient, we recommend the use of Hudson before installing the plug-in.

Hudson automatically downloads the plugin via the network, and updates the plugin via "Update".

If you cannot connect to the extranet, you can copy the plugin from the Hudson that has already been installed, and the Hudson plug-in suffix is HPI, which is then installed through the "advanced"-"Upload plugin".

HUDSON the default plugin save directory is: Hudson_home/plugins, so you can also directly copy the plug-in to the directory, restart HUDSON can be.

Hudson_home:hudson's home directory, which defaults to the current user home directory. HUDSON

You can see the specific path information in system administration-the home directory in system settings. A follow-up on the contents of the Hudson home directory.

Configuration1. Enter the required plug-in for http://localhost:8080 installation. Hudson BIRT Charts Plugin (required) JNA Native support Plugin (required) XPath Provider Plugin (required) After successful installation, click the "Finish" button at the bottom of the page to enter the main screen. 2. Go to "Install as Windows Server", "System Management", and install Hudson as a system service. 6. Go to "System settings" and "Management plug-in" to search for the feature plug-in to install. Plugin list: Hudson MSBuild Plugin Hudson Subversion plug-in7 (Hudson service will need to restart after the plugin is installed). Restart the Hudson service, go to System Management, configure MSBuild in system settings, and then click the Save button at the bottom of the page to save the configuration. Note: Name can be any name, and different versions of Visual Studio have a different version of the. NET Framework, and you want to choose a version of the. NET Framework that corresponds to Visual Studio. New Task1. Enter the task name and select "Build a free-style software project" 2. In the "Source Code Management" entry, select "Subversion", enter "Repository URL", click "Enter Credential" link into "Subversion Authentication", Enter the SVN user name and password. 3. Add the Build step ("Build", "Add Build Step") to add as many different types of steps as you need. "Build a Visual Studio project or solution using MSBuild": Core step, compile project required. Execute Windows Batch command: Perform a series of Windows commands, such as copy, "Build a Visual Studio project or solution using MSBuild" Step configuration: Msbuil D version: Select the MSBuild name that we set in the system settings, and if there are multiple versions of MSBuild configured on the machine, you can choose the appropriate version. MsBuild Build file: Fill in the location of the. sln or. vcproj files. （ Relative location to the workspace fileCommand line Arguments: Fill in the arguments that need to be passed to MSBuild. For example, to compile Foo.sln in the p1,p2,p3 of the three projects, but the order must be 2->3->1, then you can pass this parameter:/P:CONFIGURATION=RELEASE/T:P2;P3;P1, if you want to do a clean Build, you only need to add clean to the first target before/P:CONFIGURATION=RELEASE/T:CLEAN;P2;P3;P1. Click the "Save" button to save the configuration after the setup is complete. BuildSelect an item click "Build Now" to start building, click "command line Output" To view the build log. After the build succeeds, open the path "D:\Hudson\jobs\TestHudsonBuildJob\workspace\TestProject\release" to see the resulting file.

Transferred from:http://hanqunfeng.iteye.com/blog/856192

Http://www.cnblogs.com/china-jeffery/p/3449566.html

hudson--Plug-in management