maven-Creating Hudson Tasks
maven-using Hudson for continuous integration and system configuration
1 Monitoring Task status
Hudson provides a rich graphical interface that allows users to link the current and historical state of individual characters from all aspects, including a holistic list display,Customize views, specific information for individual tasks, such as build logs and test reports. Users should, based on the information provided by Hudson ,The integration task is stable in a healthy state.
1.1 Global Task status
The default home page for Hudson shows the status of all integration tasks on the current server.
This page is composed of four main parts:
navigation menu, build queue, build status, Task status (right section)
what needs to be explained is the current state and the spherical icon under the first column (S) in the diagram. Hudson uses a variety of colors to indicate the current state of a task:
--Blue: The most recent build of the task was successful.
--Red: The most recent build of the task failed.
--Yellow: The last component of the task was successful, but not stable (mainly because of a failed test).
--Gray: The task has never been executed or is disabled.
If the icon is blinking, the task is performing a build once.
The second column of Weather (W) in the figure also needs to be explained. Hudson uses a set of weather icons to indicate a long-term status for a task:
The integration of more than 80% of the mission is successful.
with a slight cloud, the task has a 60%-80% integration that is successful.
cloud-dense, mission-only 40%-60% integration was successful.
the integration success rate of the task is only 20%-40%.
Thunder and Lightning, mission integration success rate of less than 20%.
when the team sees that the integration status of the task is not healthy, it should take steps to fix the problem as soon as possible.
1.2 Customizing the task view
In general, as long as the company projects a lot of time, the continuous integration server will often have a lot of tasks, Hudson Default view will list theThere are tasks on the server, too many tasks will cause the inconvenience of finding. For this Hudson allows users to customize the view, select only the list of interestedtasks, you can even customize the columns displayed in the view. users can click the plus sign (+) next to the default view all to add a custom view:
1.3 Individual task status
in the Tasks view, click a task name to see the status of the task further.
The lower-left corner has a build history with the last 3 build histories, including component time. There are 3 permanent links below that point to the most recentBuilt , the last failed build, and the last successful build. Regardless of build history or permanent connection, we can click on a build toto solve more specific information.
, I was looking at the build of # #.
You can also view changesets and command-line output information
2 Hudson User Management
Unlike the general software user Management method, when using Hudson, do not need to actively create users, Hudson can access the source repositoryautomatically obtain user information and store them. This greatly simplifies the steps of user management. This is used here because it binds to the Subversion repository. There is no need to configure the appropriate user.
Of course, just knowing the user name is not enough, but also need to add details to the user, the most important of which is the e-mail address, because it will beused to send message feedback. Click a user's name, and then click Settings on the left side of the page, in the User Settings page on the left, you can configure the user's name, a brief descriptionpersonalized views and the most important e-mail addresses,
3 Hudson working Directory
The various configurations, tasks, and reports of Hudson are certainly stored in the form of files on disk. By default, Hudson uses the user's. hudson/directory as its working directory. C:\Users\Administrator\.hudson
A typical Hudson working directory contains content such as:
*.xml: These XML files are the configuration of the Hudson core and related plug-ins, such as the configuration of the global JDK, task view, etc. Hudson.tasks.Maven.xml Configuration of Maven installation information, Hudson.tasks.Mailer.xml configuration of mail server information, and so on.
War: If the user runs Hudson.war independently, the content will be released to that directory after it is started.
The user information stored by the Users:huson.
Usercontent: The user can place any content in the directory after it is accessed through a subpath on the Hudson Service page. such as: http://192.168.1.1:8080/userContent
Updates: A variety of updatable plugin information is stored here.
Plugins: All Hudson Good spreads are installed in this directory without affecting the core of Hudson.
Jobs: This directory contains all the configuration of Hudson Tasks, the building of storage, the build output of archives, and so on.
The most important of these directories is the jobs subdirectory, which contains all the Hudson's task configurations, the workspace of each task, and the component history.
Maven-hudson monitoring tasks, user management, working directory
