Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-3540

Build didn't execute the goal properly from hudson

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Blocker Blocker
    • emma-plugin
    • None
    • Platform: All, OS: Linux

      Hello,

      I've my pom.xml configured like

                     <plugin> 
                              <groupId>org.codehaus.mojo</groupId> 
                              <artifactId>emma-maven-plugin</artifactId> 
                              <executions> 
                                      <execution> 
                                              <phase>package</phase> 
                                              <goals> 
                                                      <goal>emma</goal> 
                                              </goals> 
                                      </execution> 
                              </executions> 
                      </plugin> 
      

      After kicking off build from Hudson, I noticed for some reason this plugin
      didn't run properly. I mean i went work
      $HUDSON_HOME/jobs/project_name/workspace/workspace_name/target/site, hudson
      didn't create emma folder insdie 'site' folder. However if I run the kick the
      build manually like mvn clean install it creates 'emma' folder inside site and
      it has coverage.xml.

      Since automatic build kick-off from hudson didn't create coverage.xml inside
      target/site/emma, my build failed and console showing the following exception
      trace. Any help in this regard highly appreciated.

      java.lang.NullPointerException 
              at org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteConfiguration(DefaultLifecycleExecutor.java:747)
              at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:578)
      

            kohsuke Kohsuke Kawaguchi
            rsemburakkiannan Raghu
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: