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

Option to Disable Parsing pom in jenkins during maven build.

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Jenkins ver. 1.625.3
      maven-plugin 2.12.1

      We are working with internal maven extension which will set the maven properties on the fly during maven run, but maven build form jenkins build fails in parsing as unable evaluate the properties used in the pom files (seems parsing doesn't call maven internally).

      Is it possible to disable parsing in someway ?

      in below "groupId" property set by maven extension.
      14:15:00 Parsing POMs*14:15:10* ERROR: Failed to parse POMs*14:15:10*
      java.io.IOException
      : remote file operation failed: workspace/Module_Build at hudson.remoting.Channel@7cdee4ed:: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:14:15:10 [ERROR] 'dependencies.dependency.groupId' for ${groupId}:commons:jar with value '${groupId}' does not match a valid id pattern. @ line 66, column 13

          [JENKINS-44057] Option to Disable Parsing pom in jenkins during maven build.

          Hi,

           

            If we disable the POM parsing (which is crappy I admit) you are loosing all advantages/features of the maven job. In that case it is better to just use a freestyle job with a Maven Builder.

           

          WDYT ?

          Arnaud Héritier added a comment - Hi,     If we disable the POM parsing (which is crappy I admit) you are loosing all advantages/features of the maven job. In that case it is better to just use a freestyle job with a Maven Builder.   WDYT ?

          Hi,

          Yes freestyle job is an option, with freestyle job we will loose other features of maven job like "incremental build"

          Reddysekhar Gaduputi added a comment - Hi, Yes freestyle job is an option, with freestyle job we will loose other features of maven job like "incremental build"

          No because "incremental builds" requires to know which files and changed in your SCM and then to map them with your maven modules to relaunch the build with the required -pl -amd options. Thus POMs have to be parsed to know which module is in which folder

          Arnaud Héritier added a comment - No because "incremental builds" requires to know which files and changed in your SCM and then to map them with your maven modules to relaunch the build with the required -pl -amd options. Thus POMs have to be parsed to know which module is in which folder

          Your real need is not to disable the Parsing POM but to allow the usage of maven extensions: JENKINS-30058 

          Arnaud Héritier added a comment - Your real need is not to disable the Parsing POM but to allow the usage of maven extensions:  JENKINS-30058  

            Unassigned Unassigned
            rgaduput Reddysekhar Gaduputi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: