Hudson

Hudson reactor plugin

A new Job type designed to configure a flow of pre defined jobs in a Hudson / Jenkins instance.

The Reactor job type will define Phases, each phase will invoke jobs in parallel.

 

Whilst introducing a Reactor Job type and enabelng each job to have it's own behavior when executed seperatelly. We will define a view which will list the execution chain of events, The Reactor acting as the top level invoker which in turn will call each Phase defined in the Recator's configuration.

 

Session targets:

1. Reactor job configuration

admin 24/02/2011 - 13:12

What a great way to conclude 2010 - maven 3 Job support in Hudson.

I know what I am going to do today ... :)

 

 

 

 

Release announcment on hudson-ci.org:

hagzag 04/01/2011 - 09:18

Yesterday we had a meetup of israeli Hudson users with Kohsuke Kawaguchi

 

Kohsuke gave a presentation about current status of Hudson and future roadmap and it followed by Q&A session.

 

Most questions involvend trying to "push the limits" of Hudson:

ittayd 21/10/2010 - 07:03

JBoss, Selenium, Maven, Hudson, M2 Extra Steps & Files Found Trigger plugins - how do all these work together in a continuous build + Integration test life-cycle ?

 

The Story - The Use Case:

We have two projects with two war artifacts which need to be deployed to a JBoss Application Server, whilst both webapps share a common base configuration, although the release life-cycle of each war have no correlation to the other.

In production both application servers are running & serving one another thus, Integration test should cover both JBoss instances & test their web services.

hagzag 12/09/2010 - 23:10

I had tow motivations of getting rid of the All view

  1. The All view is quite annoying don't you think? After using Hudson for a while you have tens/hundreds of jobs lined up in a huge list - who needs that right.
  2. I wanted a "hidden jobs section" - Jobs no one but myself (and who ever needs access to it) can see.

 

In order to get rid of it (the All view) simply:

hagzag 01/09/2010 - 10:09

As a big fan of hudson-ci I would like to take a note of the most commonly used hudson plug-ins (at least by me) needed in order to maintain a good build environment.

This list was collected as part of my experience in the last couple of years. I am sure your may differ then mine mine :).

 

Setenv plugin

hagzag 27/08/2010 - 15:30

Background:

In one of my previous projects I was asked to setup the environment / automate integration tests (Referred to as Itest from now on) which required a machine with 2 CPU's & 5 GB RAM, this means that in any case a developer wishing to run Itests will never be able to run them locally, and will have to use some existing server.

 

The problem with my previous statement is that the developer, whilst checking his tests will be busy most of the time preparing his Itest environment, rather then checking the integrity of his tests, need I say that the fact we need 2 CPU's & 5GB RAM means the server takes time to load and only once it is up you can start testing.

 

hagzag 06/12/2009 - 06:39

A neat addition to your Hudson Continues Integration server, is the Hudson Backup plug-in.

If you are during a major change in your build configuration, backup your configurations and you can restore from the backup when / if needed.

It is just much more elegant then copying those XML file's and editing them by hand when in comes to restoring your configuration... believe me I've been there ... (tested with Hudson 1.327 and 1.335 which is one release since the latest).

hagzag 26/11/2009 - 09:48

Sonar enables you to collect, analyze and report metrics on source code.

Sonar not only offers consolidated reporting on and across projects throughout time, but it becomes the central place to manage code quality.

Sonar currently covers Java and PL/SQL languages. However, Sonar is highly extensible and can therefore embark plugins to cover new languages.

 

http://sonar.codehaus.org/

 

Very simple to install: http://docs.codehaus.org/display/SONAR/Install+Sonar

and use:

http://docs.codehaus.org/display/SONAR/Analyzing+Java+Projects

 

There is also Hudson plugin that makes it even simplier to run sonar on the build server: http://wiki.hudson-ci.org/display/HUDSON/Sonar+plugin

 

 

liya 14/10/2009 - 15:20

 For thoese where waiting for documentation on hudson, you can find it at:

http://www.eclipse.org/hudson/hudsonbook/

 

Chaim Turkel 15/11/2011 - 21:48
Syndicate content