-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
- jenkins + maven plugin 1.438
- jenkins 1.466.1
It seems in my Maven2 project jenkins tries to load modules and fails because i haven't checked them out.
- I have a parent pom.xml with 3 modules in it ( Flat layout )
- But i let the parent project get checked out
- The <modules> are specified inside a "modules" profile.
- The profile is per default active. BUT, it disable it for this build via "-P!modules"
-> So a manual Maven Build on the commandline works.
But Jenkins fails, because it tries to load the pom of one of the other modules, which aren't there. Now I cannot build.
So:
- Jenkins should respect profile activateino i pass in at "Goals and options".
- when jenkins internal parsing fails, there is no reason the jenkins build itself fails.
LOG:
Parsing POMs
ERROR: POMs konnten nicht geparst werden
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-readable POM /srv/jenkins/jobs/p1-parent/workspace/p1-parent/../p1-common/pom.xml: /srv/jenkins/jobs/p1-parent/workspace/p1-parent/../p1-common/pom.xml (No such file or directory) @
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:322)
at hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1307)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1214)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1032)
at hudson.FilePath.act(FilePath.java:785)
at hudson.FilePath.act(FilePath.java:767)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:897)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:647)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:470)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Email was triggered for: Failure
So the real problem seems to be that profiles are not respected when Jenkins parses the POMs, right? Could please update the title, so this gets more clear?
Also could you please search for duplicate issues? As, if this is really not working, this is probably already reported.