Jenkins Official Document Learning notes first acquaintance Jenkins

2. What is Jenkins?

   Jenkins is a rewarding application for monitoring repetitive work, such as building a software project or performing tasks on a timed basis.

   In these efforts, Jenkins focuses on the following two tasks:

   1, continuous build/test software project, Jenkens provides a simple and easy-to-use so-called continuous integration System, allowing developers to integrate changes into the project to become more simple, so that users get a new build. Automated, continuous integration increases productivity.

   2, monitor external call execution, such as cron jobs and procmail jobs, even if these functions are running on a remote machine. For example, in a timed task, you receive regular messages that capture the output, and you have to check them regularly and notice when something goes wrong. Jenkins retains these outputs, and it's easier for you to notice when something goes wrong.

4. Who is using Jenkins?

   A lot of companies and organizations are using it. Most are used inside firewalls, but Google can tell you publicly visible examples. We have also collected some statistics from the anonymous use survey here .
   

6. Jenkins features:

   1, easy to install, as long as you use Java-jar Jenkins.war or deploy it to a server container environment. No additional installation, no database involved.

   2, easy to configure, Jenkins can complete the configuration from its friendly GUI interface with a lot of instant error checking and online Help.

   is no longer configured manually by XML, and you can do this if you want to do so.
   

   3, changeset support, Jenkins can build a list of changes from Svn/cvs, which is also done in a very efficient way to reduce the repository load

   4, permalink, most of Jenkins's pages provide clean-scale URLs, Includes some permalink "latest build"/"Latest Successful build" so you can easily link

   5,rss/e-mail/im integration from somewhere else by rss/email/ Im monitoring builds get real-time error prompts.

   6, post-mortem: Build is long tagged after build completes

   7,junit/testng test Report: JUnit test reports can be tabular, summarized, and presented in a historical phase, such as when it started breaking, The history is drawn in a chart.

   8, distributed build: Jenkins can distribute build/test loads to multiple computers. This allows you to take full advantage of the developer's idle workstations.

   9, file fingerprinting: Jenkins can track which jar files are built at which build, and which build is using which version of the jar package.

   Even the jar packages generated outside of Jenkins are still valid, and the project's independent tracking performance is perfect.

   10, plug-in support: Jenkins can be extended by third-party plugins, and you can develop plugins that let Jenkins support the tools and processes your team uses.

8. Jenkins Best Practices:

   The practice of continuous integration and continuous testing has been widely used in recent years. The concept of
   

   Continuous integration has changed how enterprises view build management, Release management, automated deployment, and testing of business processes.
   

   This section provides a set of Jenkins best practices, a continuous integration solution for business managers, business managers, software developers, and architects to better understand project development progress and code quality throughout the development cycle.

   (View Jenkins best Practices)

10. Getting Started article:

    http://linsolas.developpez.com/articles/hudson/(French)

    http://www.slideshare.net/ carlo.bonamico/continuous-integration-with-hudson/

    Kohsuke presenting Hudson in FOSDEM (video)

    Introduction to Hudson (French)

    Introduction and Best Practice by Kohsuke (Japanese)

    Introdución a Hudson (Spa Nish)

    Kohsuke presenting Hudson in Javazone (video)

    Hawebs.net docs for Hudson (Simplified Chinese Simplified Chinese) /p>

    Hudson Wiki-hudson wiki (Simplified Chinese Simplified Chinese)

    Continuous integration in the Cloud with Hudson JavaOne 20 Presentation by Kohsuke (中文版)

    Doing more with Hudson JavaOne in presentation by Kohsuke

    Hudson Presen Tation at San Francisco JUG by Kohsuke (中文版, video and slides)

    Continuous integration with Jenkins CI (Czech)

    Dzone Ref card for Jenkins (中文版)

12. Trial:

    You can start Jenkins via the Java Web, if you want to try it. Once started, you can pass http://localhost:8080/

    Access to the Jenkins panel in your browser. Any configuration for this Jenkins will be saved in ~/. Jenkins, used to get a Jenkins to restart.

14. To install Jenkins:

    Running Jenkins requires a Java 1.6+ Runtime Environment (JRE). When you finish downloading Jnekins.war, you can start this by Java-jar Jekins.war

    Basic and use the same, except that the output is displayed in the console instead of the Web page.

    Optionally,
    

Jenkins Official Document Learning notes first acquaintance Jenkins