Maven 2.2.1 Non-resolvable parent POM on slave only

[Jean Helou]

Hi,

I have been looking at the issue tracker and the mailing archive but I
can't seem to find a reference to this problem. I have two kind of
builds running on a master and a slave.

Generic builds executing maven tasks (to run sonar) which works just
fine on both the master and the slave
Maven 2 jobs executing tasks on a project pom. theses task work just
fine on the master but fail on the slave with the error below. Please
note that
fr.example:parent:pom is present in our company specific repo but it
looks like the maven user settings are being completely bypassed.

Settings for M2_HOME and MAVEN_OPTS are defined to the correct values
in the master configuration, since it didn't seem to be passed to the
slave, I have added them to the node configuration too, the maven opts
are also defined at the project level and since that still didn't seem
to work I made sure that the jnlp slave was started from a console
with all the settings to a correct value including the maven opts and
I tried a manual build from that same console, everything works just
fine ...

I am taking any suggestion to get these build working, I don't have a
lot of experience with jenkins maybe I missed something obvious ...

ERROR: Ignore Problem expanding maven opts macros
org.jenkinsci.plugins.tokenmacro.TokenMacro
Found mavenVersion 2.2.1 from file jar:file:/D:/jtb/softs/5.0.1/apps/
apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/
org.apache.maven/maven-core/pom.properties
Parsing POMs
ERROR: Echec à la lecture des POMs
hudson.util.IOException2: remote file operation failed: D:\jenkins_home
\workspace\batch\batch at hudson.remoting.Channel@e33901:GF213061
at hudson.FilePath.act(FilePath.java:752)
at hudson.FilePath.act(FilePath.java:738)
at hudson.maven.MavenModuleSetBuild
$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817)
at hudson.maven.MavenModuleSetBuild
$RunnerImpl.doRun(MavenModuleSetBuild.java:617)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:
423)
at hudson.model.Run.run(Run.java:1362)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467)
at hudson.model.ResourceController.execute(ResourceController.java:
88)
at hudson.model.Executor.run(Executor.java:145)
Caused by: hudson.remoting.ProxyException:
hudson.maven.MavenModuleSetBuild$MavenExecutionException:
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Failure to find
fr.example:parent:pom:2.0.5 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced
and 'parent.relativePath' points at wrong local POM @ line 4, column
11

at hudson.maven.MavenModuleSetBuild
$PomParser.invoke(MavenModuleSetBuild.java:1327)
at hudson.maven.MavenModuleSetBuild
$PomParser.invoke(MavenModuleSetBuild.java:1110)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1956)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown
Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Unknown Source)
Caused by: hudson.remoting.ProxyException:
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Failure to find
fr.example:parent:pom:2.0.5 in http://repo1.maven.org/maven2 was
cached in the local repository, resolution will not be reattempted
until the update interval of central has elapsed or updates are forced
and 'parent.relativePath' points at wrong local POM @ line 4, column
11

at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:
339)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
at hudson.maven.MavenModuleSetBuild
$PomParser.invoke(MavenModuleSetBuild.java:1283)
... 12 more
batch-TG-TI est désactivé. Lancement non fait.
Finished: FAILURE

[Olivier Lamy]

which jenkins version are you using ?
Is your company repo defined in the settings.xml ?

2011/4/26 Jean Helou <jean....@gmail.com>:

--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy

[Vincent Hardion]

Do you try to build directly from your slave without Jenkins ?
Have you got the same error ?

Vincent

[Jean Helou]

I use the latest jenkis 1.409
yes the company repo is configured through the user's settings.xml
file

On 26 avr, 17:31, Olivier Lamy <oliver.l...@gmail.com> wrote:
> which jenkins version are you using ?
> Is your company repo defined in the settings.xml ?
>

> 2011/4/26 Jean  Helou <jean.he...@gmail.com>:

> > org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder. java:

[Jean Helou]

yes I tried,

"I tried a manual build from that same console, everything works just
fine ... "

where "that console" is the console I used to launch the jnlp slave.
and no I don't have the same error, from the command line it all works
fine.

jean
On 26 avr, 17:44, Vincent Hardion <vincent.hard...@synchrotron-

soleil.fr> wrote:
> Do you try to build directly from your slave without Jenkins ?
> Have you got the same error ?
>
> Vincent
>
>
>
>
>
>
>
> On Tue, 2011-04-26 at 17:31 +0200, Olivier Lamy wrote:
> > which jenkins version are you using ?
> > Is your company repo defined in the settings.xml ?
>

> > 2011/4/26 Jean  Helou <jean.he...@gmail.com>:

> > > org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder. java:

[Jean Helou]

additionnaly, both master and slave run on windows XP

On 26 avr, 17:31, Olivier Lamy <oliver.l...@gmail.com> wrote:

> which jenkins version are you using ?
> Is your company repo defined in the settings.xml ?
>

> 2011/4/26 Jean  Helou <jean.he...@gmail.com>:

> > org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder. java:

[Vincent Hardion]

From the same user and local repository ?
Can you tried to play with the maven validation level in the job's
configuration ?

[Jean Helou]

from the same user and local repo ? not sure I understand the
question:
- I opened a console, ensured that the environment variables were
identical to what was specified in the jenkins config (both master,
node and build) and used the mvn command (with clean install) from
the folder where the slave made the checkout and everything built just
fine
- I started the slave from that very same console, I expect it would
inherit the exact same environment variables.

The maven validation level is at LEVEL_MINIMAL, I also tried with
LEVEL_MAVEN_2 to no avail


On 27 avr, 10:24, Vincent Hardion <vincent.hard...@synchrotron-