aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes Hudson for CI - Maven Project Build Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "Hudson for CI - Maven Project Build" Watch "Hudson for CI - Maven Project Build" New topic
Author

Hudson for CI - Maven Project Build

Joe Harry
Ranch Hand

Joined: Sep 26, 2006
Posts: 9383
    
    2

Guys,

I'm using Hudson CI to build all my projects. It is a multi-module Maven project. I have several jobs configured. One job is the parent job and the other jobs have the parent Job as its Cascading Project.

When I try to build one of my jobs, I can see that the Job only checks out the sources from the Subversion repo but fails to build. All I see in the console output of Hudson is just the following:



What should I do to get my Maven build triggered by the job?


SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5827
    
    7

Is there a trigger defined for that job? If so, what is it?

Also, is this error occurring for the job you initiated, or for one of the cascading jobs? If one of the cascading jobs, did you job complete successfully?


JBoss In Action
Joe Harry
Ranch Hand

Joined: Sep 26, 2006
Posts: 9383
    
    2

Peter Johnson wrote:Is there a trigger defined for that job? If so, what is it?

Also, is this error occurring for the job you initiated, or for one of the cascading jobs? If one of the cascading jobs, did you job complete successfully?


There are no triggers for this job. It is occurring for the actual job and not for the Cascading job. The job seems to complete successfully but it is not calling the Maven build. It gives a Success message just by checking out from the Subversion repository. But after that there is no Maven build. Why is this is what I do not understand. Could it be the type of this job causes this effect? The job that I have configured is for a multi configuration project for different environments.

I later created another job with a freestyle project and it worked like a charm.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5827
    
    7

You are saying that the only thing the job does is the Subversion checkout, and nothing else? Doesn't that job have any build steps defined? Perhaps without a build step, Hudson is having difficulty deciding that the build was successful, and thus will not invoke any triggers.

I think you need to explain the details of the job configuration. Perhaps take screen images of the configuration and post them.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Hudson for CI - Maven Project Build