Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Hudson-ci/Containers/GlassFish"

 
Line 9: Line 9:
 
You can upgrade your existing Hudson by overwriting {{path|$GLASSFISH_HOME/domains/domain1/autodeploy/hudson.war}} with a newer version. Again, you can also do this from the admin GUI by choosing to redeploy the application.
 
You can upgrade your existing Hudson by overwriting {{path|$GLASSFISH_HOME/domains/domain1/autodeploy/hudson.war}} with a newer version. Again, you can also do this from the admin GUI by choosing to redeploy the application.
  
= Setting HUDSON_HOME =
+
= Setting HUDSON_HOME =
  
There are many ways to do this, but one way to do so is to configure Glassfish to run with the "HUDSON_HOME" system property. From the command line, do the following:
+
There are many ways to do this, but one way to do so is to configure Glassfish to run with the "HUDSON_HOME" system property. From the command line, do the following:  
{{codeblock|% ./asadmin create-jvm-options -DHUDSON_HOME=/path/to/hudson_home}}
+
You can do the same from the admin GUI as well. This technique should be also used to increase the VM heap size, when your Hudson setup gets big.
+
 
+
If you get confused or this doesn't work, just try to set {{code|HUDSON_HOME}} environment variable before launching Glassfish:
+
 
<pre>
 
<pre>
% export HUDSON_HOME=/path/to/hudson_home
+
% ./asadmin create-jvm-options -DHUDSON_HOME=/path/to/hudson_home
% ./asadmin start-domain
+
 
</pre>
 
</pre>
 +
You can do the same from the admin GUI as well. This technique should be also used to increase the VM heap size, when your Hudson setup gets big.
 +
 +
If you get confused or this doesn't work, just try to set {{code|HUDSON_HOME}} environment variable before launching Glassfish:
 +
<pre>% export HUDSON_HOME=/path/to/hudson_home
 +
% ./asadmin start-domain
 +
</pre>
 
Glassfish needs to be restarted for this change to take effect.
 
Glassfish needs to be restarted for this change to take effect.
  

Latest revision as of 05:29, 2 September 2011

Hudson Continuous Integration Server
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse Source
Hudson-bust.png Using GlassFish as a Container











Installation

To install Hudson on Glassfish, simply copy hudson.war to $GLASSFISH_HOME/domains/domain1/autodeploy. Alternatively, you can do this from admin GUI. See this document for more about this.

Upgrade

You can upgrade your existing Hudson by overwriting $GLASSFISH_HOME/domains/domain1/autodeploy/hudson.war with a newer version. Again, you can also do this from the admin GUI by choosing to redeploy the application.

Setting HUDSON_HOME

There are many ways to do this, but one way to do so is to configure Glassfish to run with the "HUDSON_HOME" system property. From the command line, do the following:

% ./asadmin create-jvm-options -DHUDSON_HOME=/path/to/hudson_home

You can do the same from the admin GUI as well. This technique should be also used to increase the VM heap size, when your Hudson setup gets big.

If you get confused or this doesn't work, just try to set HUDSON_HOME environment variable before launching Glassfish:

% export HUDSON_HOME=/path/to/hudson_home
% ./asadmin start-domain

Glassfish needs to be restarted for this change to take effect.

Securing Hudson

See the forum thread on this topic.

Back to the top