Hudson is a powerful and widely used open source continuous integration server providing development teams with a reliable way to monitor changes in source control and trigger a variety of builds. Hudson excels at integrating with almost every tool you can think of. Use Apache Maven, Apache Ant, or Gradle (or anything you can start with a command line script) for builds, and send messages via email, SMS, IRC, and Skype for notifications. In addition to providing a platform for continuous integration builds, Hudson can also be extended to support software releases, documentation, monitoring, and a number of use cases secondary to continuous integration.

Read more...

With continuous integration, the system completes a build, test, deploy, and integration in response to every single commit. If a developer in the web application group checks in code, Hudson kicks off a build, runs unit tests, deploys the code to a new server, and performs a set of integration tests. If this build fails or the tests encounter an unexpected condition, everyone is notified of this failure. With continuous integration, no one needs to drop everything and run a release build, these builds are generated every single day, and in the most mature environments, a fully tested and verified system can be deployed to production at any time. In other words, when you automate build, test, and verify using a tool like Hudson you can continue developing your applications without having to wait (or synchronize) on some manual build, test, verify process. Making these processes automatic has another important side-effect, it makes the development process more scaleable. When your teams don’t have to stop to actively test and collaborate with one another, it is much easier to add additional developers to a project. Without continuous integration you have to stop and synchronize release schedules. With continuous integration you reduce the risk associated with a particular software development cycle.

For more details about Hudson, you can refer to Hudson Documentation.

1. Download the latest hudson.war file from http://hudson-ci.org

   

2. Open a command window from the folder where you downloaded the Hudson file.

   

3. In the command window type: java -jar hudson-2.2.0.war --httpPort=8989 to install Hudson and run it on port 8989.

   

4. Wait for Hudson to finish initializing.

   

5. Open a browser window and type http://localhost:8989/ to launch the Hudson console. Wait for the Hudson dashboard page to load.

   

6. In the Hudson dashboard page, select the Manage Hudson link.

   

   Notice that in Microsoft Windows environment, you can create a Windows service for Hudson and have the service start automatically. Refer to the following link for instructions on how to install Hudson as a Windows service.

7. In the Manage Hudson page, select the Manage Plugins link.

   

8. In the Plugin Manager, click the Installed tab.

   

9. Note that the list of installed plugins includes the Hudson Subversion Plug-in. Click the Back to Dashboard link.

   

To indicate to Hudson that ojdeploy and Ant are used for building the test, perform the following steps:

1. Back in the Hudson Dashboard page, click the Manage Hudson link.

   

2. In the Manage Hudson page, click the Configure System link.

   

3. Select the Environment variables check box in the Global Properties section, then click the Add button to add a key-value pair to specify the location of the ojdeploy executable. In your case, you are not going to use the ojdeploy command, but you might need to use the command later if you choose to include packaging tasks in future builds. Therefore, it's a good idea to learn how to configure it now.

   

4. In the name field, type OJDEPLOY. Using Windows Explorer, locate the ojdeploy.exe file and copy its path in the value field.

5. Scroll down to the JDK section to specify where it is located. Click the Add JDK button.

   

6. Type JDK as the JDK Name, and in the JAVA_HOME field, specify the path to the jdk folder.

   

7. Scroll down the Manage Hudson page, and in the Ant section, click the Add Ant button.

   

8. In the Ant installations section, deselect the Install automatically check box, and then type Ant_Default as the Ant Name. Using Windows Explorer, locate the ant folder and copy its path in the ANT_HOME field.

   

9. Scroll down to the bottom of the page, and click the Save button.

   

   At this point, notice that you can set up an email notification. You learn how to do this later.

1. Back in the Hudson Dashboard, click the create new jobs link.

   

2. In the Job name field, type Hudson_Testing, select the Build a free-style software project option, and click OK.

   

3. Because you are using Subversion as the repository tool in JDeveloper, you need to specify the location of the Subversion resource files. In the Project page, select Subversion in the Source Code Management section.

   

4. In the Repository URL field, type the URL of your repository.

   

5. If you don't know the URL, you can copy it from the Versioning Navigator in JDeveloper. Right-click MyRepostory, and select Copy URL.

   

6. Paste the URL into the Repository URL field. In the Check-out Strategy field, select the Clean workspace and then checkout option from the list.

   

7. Scroll down and in the Build section, click the Ant build step button, and select the Invoke Ant option.

   

8. In the Build section under Invoke Ant, select Ant_Default for the Ant version. Type all in the Targets field.

   

   Click the Advanced button

9. In the Build File field, type JUnitTests/build.xml to indicate the relative location of the build.xml file.

   

10. Click the Save button at the bottom of the page.

Now that your job is defined, you can run it.

1. In the Hudson_Testing project, click the Build Now link to run the test.

   

2. Wait for the build to end. Then click the Latest Console output link to see the status.

   

3. The Blue circle indicates a successful run. Notice the list of executed Ant targets in the bottom left section of the page.

   

4. Scroll down to review all details.

   

   At this point, you have used Hudson to call and execute the all Ant target that you previously executed from JDeveloper.

To allow interaction between Hudson and TPC, you need to install the TPC plugin for Hudson. To install the plugin, perform the following actions:

1. Go to the Hudson plugins site and click the plugins link.

   

2. Select the HudsonTpcPlugin link.

   

3. Select the latest build folder.

   

4. Right-click the HudsonTpcPlugin.hpi file, and select the Save Target As option. Download the file in the directory of your choice (Hudson/plugin in this case).

   

5. In the Hudson dashboard, click the Manage Hudson link.

   

6. Click the Manage Plugins link.

   

7. Click the Advanced tab in the Plugin Manager page.

   

8. In the Upload Plugin section, indicate the location of the HudsonTpcPlugin.hpi file and click the Upload button.

   

9. Click the Installed tab to see the status of the new plugin. Notice the warning indicating that you need to stop and restart Hudson to activate the plugin.

   

10. Click the Hudson link to go back to the Hudson dashboard, and click the Manage Hudson link.

    

11. Scroll down and click the Prepare for Shutdown link.

    

12. Go to the Command window where Hudson is running and stop it (press Ctrl + C).

13. Close your Hudson browser window, and restart Hudson from the command line by using the command java -jar hudson-2.2.0.war --httpPort=8989.

    

14. Restart the Hudson Console in a browser window by typing localhost:8989 as the URL, then click Manage Hudson and Manage Plugins.

    

15. Click the Installed tab. The HudsonTpcPlugin should be present and ready for use.

    

You can configure Hudson to send an email to a specific email address when a build failure occurs.

1. Back in the Hudson dashboard, click the Manage Hudson link and then the Configure System link.

   

2. Scroll down to the E-mail Notification section, and specify the SMTP server address and other details about the notification. In this example, there is a local SMTP server installed. Click the Advanced button to specify additional properties.

   

3. Select the Use SMTP Authentication check box, and specify additional information to use SMTP authentication. Click the Test configuration by sending e-mail to System Admin Address button.

   

4. Click the Save button.

   

5. Open your email to verify that you received the notification.

   

6. Return to the Hudson dashboard and select the Hudson_Testing project. Click the Configure link.

   

7. Scroll down to the Post-build Actions section, and select the E-mail Notification check box. By default Hudson notifies the indicated users only when the build operation fails. If you want to get notified on success, you need to install the Hudson Email Extension Plugin.

   

8. In the Recipients field, type the email addresses of the persons in the team: miles.davis@example.com, john.coltrane@example.com, nat.adderley@example.com. Select the two check boxes to send alerts in both scenarios.

   

   Click the Save button.

You can configure Hudson to use TPC to deliver information about test results to JDeveloper.

1. In the Hudson_Testing page, click the Configure link to refine the project.

   

2. Scroll down to the Post-build Actions section, and select the Publish JUnit test result report check box.

   

3. Specify the Hudson relative path and the file name of the report file. For example: JUnitTests\testResults\TEST-model.services.AllAppModuleTests.xml.

   

4. Select the Publish test results to Oracle Team Productivity Center check box.

   

5. Type http://127.0.0.1:7001 as the URL of Oracle TPC Server and enter mdavis/Welcome1 as the TPC username/password of the user you want to inform.

   

6. Click the Test Connection button to validate the connection.

   

   Scroll down and click the Save button.

7. Switch to JDeveloper. In the Hudson Model project under model.entities, open the Departments entity.

   

8. Click the Attributes tab, and select the DepartmentName attribute. In the UI Hints tab, type Department Name as the label.

   

9. Click the Save All icon on the JDeveloper menu bar, or select File > Save All from the main menu.

10. Right-click in the Hudson Application and select Versioning > Commit Working Copy.

    

11. In the Commit Working Copy dialog, type UI Hints changes and click OK.

    

    Next, you run a build and see how JDeveloper receives information about the build from Hudson.

12. Return to the Hudson page and click the Hudson_Testing link to reopen the job.

    

13. Click the Build Now link to launch the job.

    

14. When the build is complete, click the Latest Console output link and scroll down to see the execution report.

    

    Notice the message indicating that the result will be sent to Oracle Team Productivity Server. Because the build was successful, no email notifications are sent.

15. Go back to JDeveloper, and from the main menu select View > Team > Build Dashboard.

    

16. In the Build Dashboard pane in JDeveloper, click the Hudson_Testing link.

    

17. The Hudson_Testing report shows details about the execution.

    

18. From the Show drop-down list, select All Tests.

    

19. See the detailed status at each step of the build.

    

20. Click the Build Dashboard tab and then click the Hudson_Testing row to activate the Related Transactions pane. The Related Transactions pane indicates the versioning number (19 in this example) of the latest versioned element.

    

21. Now that the connection between Hudson, TPC, and JDeveloper is established, you receive alerts each time Hudson executes a new build.

    

You've successfully completed this tutorial, which illustrates how to implement a continuous integration process.

• Install the various pieces of software required for this continuous integration tutorial
• Build a basic Fusion Web application
• Version your application using Subversion
• Connect JDeveloper to TPC
• Create users, teams, and task rules
• Install JUnit extensions in JDeveloper and create a JUnit test project
• Run the JUnit project
• Configure Ant and build a Ant test
• Install and configure Hudson server
• Create a project to run the build job
• Install the TPC plugin in Hudson
• Automate an email alert system
• Send Hudson feedback to JDeveloper

• JDeveloper and Application Development Framework
• Apache Ant documentation
• JUnit documentation
• Hudson documentation

Expand all | Hide all