wiki.hudson-ci.org/display/HUDSON/Plugin+tutorial

however, when I run the setup (mvn hpi:run), the plugin doesn’t show up as a configuration option in the Hudson Management console. It does show up as an installed plugin in the Plugin Manager. The build runs fine, Jetty starts fine, no exceptions in the console, one info-level warning about the plugin being loaded twice:

Mar 24, 2010 12:13:16 AM hudson.PluginManager$1$3$1 isDuplicate

INFO: Ignoring C:\p4\Hudson\reviewboard\.\work\plugins\testplugin.hpl because C:\p4\Hudson\testplugin\.\work\plugins\testplugin.hpl is already loaded

Any ideas why the sample wouldn’t work “out of the box”?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Hudson plugin development in Eclipse appeared first on scmGalaxy.

I have setup Hudson successfully and covered all most all the features. But Still i have some question which want to get clarify with the help of community members.

1. Each Project Build Number in Hudson and build artifact folder naming are different. How can we match up so it should be with Hudon Build number.
2. Upon successful build, how can i get the build artifact link for each build of Hudson Dashboard?

rajeshkumar replied the topic: Re:Questions on Hudson
reply from hudson community…

> 1. Each Project Build Number in Hudson and build artifact folder naming are
> different. How can we match up so it should be with Hudon Build number.

Hudson provides your build scripts an environment variable
BUILD_NUMBER which is an increasing integer. You are free to use that
or ignore it and come up with your own way of identifying your builds.

If want to increment Hudson’s build number, edit the file buildNumber
which is in HUDSON_HOME/jobs/JOBNAME and then go to Manage Hudson ->
Reload configuration files from disk.

> 2. Upon successful build, how can i get the build artifact link for each
> build of Hudson Dashboard?

If I understand you correctly, you are looking for the permalinks in
the page for each project. I.e. http://YOURHUDSON/job/JOBNAME/
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Questions on Hudson appeared first on scmGalaxy.

Today I’m going to be migrating a Hudson 1.334 instance on one machine to another machine and in the process upgrading to 1.355.

Anyone happen to have any tips or things to watch out for while
migrating servers?

I’m going to start by simply backing up my HUDSON_HOME directory and
attempting to move that, hoping it is as simple as it sounds.

The post Tips on migrating Hudson instance to new machine appeared first on scmGalaxy.

I’m wondering if it is possible to map the Hudson user name to one or more VCS user names. I’ve setup a Hudson instance with simple security (logged in people can do anything, non-logged in people can only view build results). For some reason Hudson is not mapping the users to the people that perform the checkins. So the last activity of each user is always empty. Is there a special setting that I need to know of or should Hudson automatically take care of that?

Thanks
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post How to map Hudson user names to VCS user names appeared first on scmGalaxy.

Hi, I’m looking for some advice on whether our Hudson setup is
sensible, and I’m also wondering how to poll instead of build
“dependency-triggered” jobs.

We have a project that is broken up into 3 components. As is typical
with git, each component is a standalone piece that lives in its own
git repository.

The Hudson Git Plugin takes multiple repository URLs but blends them
together, so we couldn’t just keep everything in a single job (nor do
I think we really want that), and instead we created one job per
repository.

Dependency-wise, one project (C) depends on the other two (A, B).
Brief Googling led us to the Join Plugin. So now we have a 4th “base”
job (D) that is empty and simple triggers A, B to build, then has a
Join Trigger for C. D builds every hour.

Now to the question: our setup produces a lot of unnecessary builds.
Is there a way to add polling into the chain, such that if an upstream
poll detects no changes, downstream polls still take place? It seems
that currently there are two problems standing in the way of this:

(1) Downstream jobs can only be built, not polled.

(2) Only post-build triggers exist, so an upstream project (like A or
B) must actually go through a build for C to build, whereas what we’d
want here is a post-poll trigger.

Thanks in advance for any tips

The post Advice on our Hudson setup / How to Poll Dependencies appeared first on scmGalaxy.

Questions:
I’m using Hudson and Maven and also Ant to make a build.

I need to set the ANT_OPTS to pass additional JVM arguments. But where can I
set/change the ANT_OPTS in Hudson for a project?

When I configure a project I press button ‘ADVANCED’ in the build section.
In there I can set the MAVEN_OPTS, but actually I’m searching for the
ANT_OPTS.

Because at the moment the JunitReport code which is being called by ant
within Maven I’m running out of permgen memory.

At the moment this is what I pass to MAVEN_OPTS:
-Xmx1024m -Xms1024m -XX:MaxPermSize=512m -XX:+CMSPermGenSweepingEnabled
-XX:+CMSClassUnloadingEnabled

but I really need to set the ANT_OPTS somewhere.

Answer
Try the “java options” field in the advanced section.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Where can you set/change the ANT_OPTS in Hudson appeared first on scmGalaxy.

I want a single Hudson job to control all these things, instead of creating one job for each branch, not to mention the fact that the number of branches will increase in the future.

The most important thing is, when branch A is changed and updated, I want Hudson only to build branch A, not all branches and trunk.

In a word: how can I make Hudson discriminate which directory has been changed and run the corresponding script?
How to implement this?

mnanjala replied the topic: Re:Hudson with Subversion
Hello
You should use parameterized build which and you should later give as ${BRANCH} where ever you call respective branch…

The post Hudson with Subversion appeared first on scmGalaxy.

Let say Hudson+Jira and SVN are integrated and we are planning to release a build.
While execution of job we can identify how many tickets are fix during a unique build but how we are going to identify the tickets which are not fixed during the same build?
Build server should send an email notification of Tickets which are not fixed during that build?

Thanks in advance
Amit

rajeshkumar replied the topic: Jira issue not fixed via hudson
I know i am replying late but I am looking for similar solution now a days? Can you please share your experience on it?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Jira issue not fixed via hudson appeared first on scmGalaxy.

Remote file system root does not exist. Will try to create it…

[10/31/13 01:36:55] [SSH] Opening SSH connection to 172.16.116.77:22.
[10/31/13 01:36:56] [SSH] Authentication successful.
[10/31/13 01:36:57] [SSH] The remote users environment is:
BASH=/bin/bash
8d03be7b734b352178df5-1383227978.473831-1761971970
_=’]’
[10/31/13 01:36:57] [SSH] Checking java version of java
[10/31/13 01:36:58] [SSH] java -version returned 1.7.0_25.
[10/31/13 01:36:58] [SSH] Starting sftp client.
[10/31/13 01:36:58] [SSH] Remote file system root does not exist. Will try to create it…
hudson.util.IOException2: Could not copy slave.jar into ” on slave
at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:790)
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:487)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: hudson.util.IOException2: Failed to mkdir
at hudson.plugins.sshslaves.SFTPClient.mkdirs(SFTPClient.java:85)
at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:762)
… 7 more
Caused by: com.trilead.ssh2.SFTPException: No such file (SSH_FX_NO_SUCH_FILE: A reference was made to a file which does not exist.)
at com.trilead.ssh2.SFTPv3Client.expectStatusOKMessage(SFTPv3Client.java:555)
at com.trilead.ssh2.SFTPv3Client.mkdir(SFTPv3Client.java:955)
at hudson.plugins.sshslaves.SFTPClient.mkdirs(SFTPClient.java:83)
… 8 more
[10/31/13 01:36:59] [SSH] Connection closed.

rajeshkumar replied the topic: hudson.util.IOException2: Could not copy slave.jar into ” on slave
Check if “Remote FS root” in slave configurtion…
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post hudson.util.IOException2: Could not copy slave.jar into ” on slave appeared first on scmGalaxy.

scmuser replied the topic: The hudson service on local computer started and stopped
Solved that problem
I cleared the event log, then it worked.. the application log was full so it couldn’t start..

The post The hudson service on local computer started and stopped appeared first on scmGalaxy.

Could you please let me know “How to un-installed Hudson service from nodes”?

-Sm

scmuser replied the topic: How to un-installed Hudson service from nodes
To uninstall the service, run hudson-slave.exe uninstall from the command line. The Hudson-slave executable can be found in the slave root directory. Note that you should run the uninstall from a admin command prompt on Windows 7 and the service will not be removed until the service is manually stopped or the Windows machine is re-booted. you can also manually uninstall the service using the command: sc delete Hudson Slave, again issue this from an admin console.

The post How to un-installed Hudson service from nodes appeared first on scmGalaxy.

The post Hudson appeared first on scmGalaxy.

The tasks can be scheduled to run on the same machine (Master), or on a different machine (Slave). A master is a installation of Hudson, that can manage one or more slaves. The role of master remains same in Master slave setup. It serves HTTP requests, and it can still build projects on it’s own.

Slaves are computers that are setup to build projects triggered from the master. A separate program called slave agent runs on slave computer. In this article we’ll discuss about how to setup Hudson to executed distributed builds using Master slave. One computer can be configured to execute multiple slave agents.

How it works

When the slaves are registered to a master, the master starts distributing loads to slaves. The delegation depends on the specific job. The job can be configured to either execute on the master, or it can be tied to a specific slave. On the other hand, the jobs can be configured to freely roam between slaves, wherein the job is executed using the free slave. As per the user is concerned, the setup is transparent. The results for all jobs are viewable using the Master, irrespective of the Slave that executed the job.

The slave may be built using any Operating system. The Master slave setup is highly helpful while the user has to execute the job on different Operating system. Consider this use case: The application is expected to run on different operating system, Linux, Solaris and Windows system. To address this need, the user can install Hudson on any machine, say Linux, and add 2 slaves: Solaris and Windows. The user can add 3 different jobs, one running on Master itself and others running on slave machines.

Methods to set up Slave agents

The slave can be launched from Master using any of below methods:

1. Launch Slave agents on Unix machines via SSH.
2. Launch Slave agents via JNLP.
3. Launch Slave agents via execution of command on the master.
4. Let Hudson control windows slave as a windows service.

The following screenshot illustrates the list of modes under which the Hudson slave can be launched.

Set up Slave agents on Unix machines via SSH

Hudson has a built-in SSH client implementation that it can use to talk to remote sshd and start a slave agent. This is the most convenient and preferred method for Unix slaves, which normally has sshd out-of-the-box. Click Manage Hudson, then Manage Nodes, then click New Node. In this set up, the connection information is supplied, including SSH host name, user name and authentication credentials. The authentication is performed using password or ssh keys. If it is configured to use ssh keys, the SSH public key should be copied to ~/.ssh/authorized_keys file. Hudson will do the rest of the work by itself, including copying the binary needed for a slave agent, and starting/stopping slaves.

 

Depending on the project and hardware resource availability, the user Desktop can be used as one of Slave, without affecting his day-to-day activities, thus avoiding the need for dedicated Slaves.

Establish slave agent via Java Web Start

Another way of launching slave is to start a slave agent through Java Web Start (JNLP). In this approach, the user will login to the slave node, open a browser and open the slave page using the URL pointed to the Master. It may look like the following URL:

http://masterserver:port/hudson/jnlpJars/slave.jar

The user is presented with the JNLP launch icon. If user click the icon, the Java Web Start kicks in and it launches a slave agent on this computer.

This mode is convenient when the master cannot initiate a connection to slaves, such as when it runs outside a firewall while the rest of the slaves are in the firewall. The disadvantage is, if the machine with a slave agent goes down, the master has no way of re-launching it on its own.

Set up slave agent headlessly

This launch mode uses a mechanism very similar to Java Web Start, except that it runs without using GUI, making it convenient for an execution as a daemon on Unix. To do this, the user should configure this slave to be a JNLP slave by downloading slave.jar, and then from the slave, run a command like this:

java -jar slave.jar -jnlpUrl http://yourserver:port/computer/slave-name/slave-agent.jnlp

The slave.jar file is downloaded from the above mentioned URL. Make sure to replace slave-name with the name of the slave setup in Master.

By default, Hudson runs on port 8080. It can be installed and managed without the need for super user privilege. The super user privilege is not required to manage both Master and Slave.

The below diagram illustrates the list of configuration parameters specific to a slave.

 

set up Slave Agent using own scripts

If the above modes is not flexible, the user can write his own script to launch the Slave agent. The script is placed in the Master computer and Hudson runs this script whenever it should connect to the slave. The script may use the remote login program like SSH, RSH to establish connection between Master and slave.

The script would execute the slave agent program like java -jar slave.jar. The stdin and stdout for the script should be connected to the master. For example, the script that does ssh myslave java -jar ~/bin/slave.jar would satisfy this need, when it is executed from the Master web interface. For this reason, running this script manually from the command line does no good.

The copy of slave.jar can be downloaded from the above mentioned URL. Launching the slave agent using this mode requires additional setup in the Slave. The benefit is that when the connection goes bad, the user can use Hudson web interface to re-establish the connection.

The post How to Setup Configure Hudson Master Slave? – Complete Guide appeared first on scmGalaxy.