Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Hudson-ci/Using Hudson/Installing Hudson"
| (13 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{Template:hudson|pageTitle=Installing Hudson}} | + | {{Template:hudson|pageTitle=Installing Hudson}} |
| − | + | ||
| − | Hudson | + | == Distributions == |
| + | Hudson can be downloaded from both [http://www.eclipse.org/hudson/download.php eclipse.org] and [http://hudson-ci.org hudson-ci.org]. More information about the available distributions can be found [http://wiki.eclipse.org/Hudson-ci/development/releaseartifacts here]. | ||
| − | |||
| − | + | == Prerequisites == | |
| − | + | Hudson only needs a Java 6 or newer runtime. An internet connection will be required if you want to be able to install and auto-update plug-ins. | |
| − | |||
| − | + | == WAR file == | |
| − | + | After you download [http://www.eclipse.org/hudson/download.php hudson.war], you can launch it by executing {{Template:code|java -jar hudson.war}}. This is mostly useful for testing purposes. For production we recommend using native packages for simplified install or deployment in a servlet container that supports Servlet 2.4/JSP 2.0 or later, such as Glassfish, Tomcat 5, JBoss, Jetty 6, etc. See [[Hudson-ci/Containers|Containers]] for more about container-specific installation instruction. | |
| − | + | ||
| − | + | ||
| − | + | Once the war file is exploded, run {{Template:code|chmod 755 hudson}} in the exploded {{Template:path|hudson/WEB-INF}} directory so that you can execute this shell script. | |
| − | + | == Unix/Linux Installation == | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | The Hudson project provides native packages for various Linux distributions. These are the simplest way to run Hudson in production, since the packages set up user, service and all other configuration as well as integrate with the native upgrade mechanism of the operating system. | |
| − | + | ||
| − | + | *[[Hudson-ci/Installing Hudson DEB|Installing Hudson on Ubuntu and Debian]] | |
| + | *[[Hudson-ci/Installing Hudson RPM|Installing Hudson on Oracle Enterprise Linux, RedHat, CentOS & Fedora ]] | ||
| + | *[[Hudson-ci/Installing Hudson SUSE|Installing Hudson on openSUSE]] | ||
| − | + | For other operating systems check out the following pages for help. | |
| − | + | *[[Hudson-ci/Installing Hudson Unix Daemon|Installing Hudson as a Unix daemon]] | |
| + | *[[Hudson-ci/Installing Hudson Gentoo|Installing Hudson on Gentoo]] | ||
| + | *[[Hudson-ci/Installing Hudson FreeBSD]] | ||
| + | *[http://pauloswald.com/blog/article/29/hudson-solaris-smf-manifest Installing Hudson as Solaris 10 service] | ||
| − | + | Alternatively, if you have a servlet container that supports Servlet 2.4/JSP 2.0, such as Glassfish v2, Tomcat 5 (or any later versions), you can run them as services, and deploy '''hudson.war''' as you would any other war file. [[Hudson-ci/Containers|Containers]] documentation is available if you choose this route. | |
| − | + | ||
| − | + | == Windows Installation == | |
| − | + | If you're running on Windows you might want to run Hudson as a service so it starts up automatically without requiring a user to log in. The easiest way is follow [[Hudson-ci/Installing Hudson Windows Service|Installing Hudson as a Windows service]]. Alternatively, you can install a servlet container like GlassFish and Tomcat, which can run as a service by itself, and then deploy Hudson to it. | |
| − | + | Since Hudson was written to work on unix-like platforms, some parts assume the presence of unix-utilities. It is advised to install these as well on Windows. Install [http://unxutils.sourceforge.net/ UnxUtils] (this includes a shell that seems to work with forward and backwards slashes and does globbing correctly), put it in the Windows {{Template:Code|PATH}}, and copy {{Template:Code|sh.exe}} to {{Template:Path|C:\bin\sh.exe}} (or whichever drive you use) to make shebang lines work. This should get you going. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | [ | + | If you're running on Windows you might want to run Hudson as a service so it starts up automatically without requiring a user to log in. One way is to first install Tomcat as a service and then deploy Hudson to it in the usual way. Another way is to use the [http://wrapper.tanukisoftware.org/doc/english/introduction.html Java Service Wrapper]. However, there may be problems using the service wrapper, because the Main class in Hudson in the default namespace conflicts with the service wrapper main class. Deploying inside a service container (Tomcat, Jetty, etc.) is probably more straightforward, even for developers without experience with such containers. |
| + | |||
| + | *[[Hudson-ci/Installing Hudson Windows Service|Installing Hudson as a Windows service]] | ||
Revision as of 03:45, 12 January 2013
| Hudson Continuous Integration Server | |
| Website | |
| Download | |
| Community | |
| Mailing List • Forums • IRC • mattermost | |
| Issues | |
| Open • Help Wanted • Bug Day | |
| Contribute | |
| Browse Source |
|
Installing Hudson |
|---|
Contents
Distributions
Hudson can be downloaded from both eclipse.org and hudson-ci.org. More information about the available distributions can be found here.
Prerequisites
Hudson only needs a Java 6 or newer runtime. An internet connection will be required if you want to be able to install and auto-update plug-ins.
WAR file
After you download hudson.war, you can launch it by executing java -jar hudson.war. This is mostly useful for testing purposes. For production we recommend using native packages for simplified install or deployment in a servlet container that supports Servlet 2.4/JSP 2.0 or later, such as Glassfish, Tomcat 5, JBoss, Jetty 6, etc. See Containers for more about container-specific installation instruction.
Once the war file is exploded, run chmod 755 hudson in the exploded hudson/WEB-INF directory so that you can execute this shell script.
Unix/Linux Installation
The Hudson project provides native packages for various Linux distributions. These are the simplest way to run Hudson in production, since the packages set up user, service and all other configuration as well as integrate with the native upgrade mechanism of the operating system.
- Installing Hudson on Ubuntu and Debian
- Installing Hudson on Oracle Enterprise Linux, RedHat, CentOS & Fedora
- Installing Hudson on openSUSE
For other operating systems check out the following pages for help.
- Installing Hudson as a Unix daemon
- Installing Hudson on Gentoo
- Hudson-ci/Installing Hudson FreeBSD
- Installing Hudson as Solaris 10 service
Alternatively, if you have a servlet container that supports Servlet 2.4/JSP 2.0, such as Glassfish v2, Tomcat 5 (or any later versions), you can run them as services, and deploy hudson.war as you would any other war file. Containers documentation is available if you choose this route.
Windows Installation
If you're running on Windows you might want to run Hudson as a service so it starts up automatically without requiring a user to log in. The easiest way is follow Installing Hudson as a Windows service. Alternatively, you can install a servlet container like GlassFish and Tomcat, which can run as a service by itself, and then deploy Hudson to it.
Since Hudson was written to work on unix-like platforms, some parts assume the presence of unix-utilities. It is advised to install these as well on Windows. Install UnxUtils (this includes a shell that seems to work with forward and backwards slashes and does globbing correctly), put it in the Windows PATH, and copy sh.exe to C:\bin\sh.exe (or whichever drive you use) to make shebang lines work. This should get you going.
If you're running on Windows you might want to run Hudson as a service so it starts up automatically without requiring a user to log in. One way is to first install Tomcat as a service and then deploy Hudson to it in the usual way. Another way is to use the Java Service Wrapper. However, there may be problems using the service wrapper, because the Main class in Hudson in the default namespace conflicts with the service wrapper main class. Deploying inside a service container (Tomcat, Jetty, etc.) is probably more straightforward, even for developers without experience with such containers.