[
https://issues.jenkins-ci.org/browse/JENKINS-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161451#comment-161451
]
Bruno P. Kinoshita commented on JENKINS-12977:
----------------------------------------------
Hi there,
I was having the same issue here, using Jenkins ver. 1.447.1, running mvn clean
test install site
Interesting that dropping the site option it works. And if I executed the same
command as normal user, including the site goal, it would run (jenkins had its
own user).
Then I noticed my user had ./m2/settings-security.xml and user/password
configured in settings.xml.
I copied the settings-security.xml to $jenkins_user_home_directory/.m2 and it's
working again. In my case, I believe it was an issue with maven site and
sonatype (the parent of my project was sonatype 5).
http://jira.codehaus.org/browse/MSITE-81
HTH
> Unable to build maven2 project with maven2/3 native jobs "Not authorized,
> ReasonPhrase:Unauthorized"
> ----------------------------------------------------------------------------------------------------
>
> Key: JENKINS-12977
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12977
> Project: Jenkins
> Issue Type: Bug
> Components: maven, maven2
> Environment: jenkins-LTS-1.424.3 (issue was not there in LTS-1.424.2)
> Reporter: batmat
> Priority: Critical
> Labels: maven, native
>
> Since the upgrade to Jenkins-1.424.3, we are unable to build a native maven
> build on maven2 projects.
> Seems like it's trying to parse the project's pom, and it won't succeed.
> Might be related to the bigger strictness of M3, but from a m2 project point
> of view, it's a regression :-/.
> {quote}
> {noformat}
> L'ééchéance d'une alarme périodique a provoqué le lancement de ce job
> ln -s 2012-03-02_07-28-27 /ic/.jenkins/jobs/someproject-10.0/builds/517
> failed: -1
> Building on master
> Updating svn://somesvn/someproject-parent
> At revision 69492
> no change for svn://somesvn/someproject-parent since the previous build
> No emails were triggered.
> Parsing POMs
> Failed to transfer Not authorized, ReasonPhrase:Unauthorized.
> ERROR: Echec à la lecture des POMs
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM: Could not transfer artifact
> fr.gid:someartefact:pom:11.5.0 from/to devRepo
> (http://repository.corp.net:8081/nexus/content/groups/public/): Not
> authorized, ReasonPhrase:Unauthorized. and 'parent.relativePath' points at
> wrong local POM @ line 5, column 10
> 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:1355)
> at
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1182)
> at hudson.FilePath.act(FilePath.java:758)
> at hudson.FilePath.act(FilePath.java:740)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:869)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:634)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:458)
> at hudson.model.Run.run(Run.java:1376)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:487)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:175)
> [WARNINGS] Skipping publisher since build result is FAILURE
> Saut de l'analyse sonar suite à un mauvais status de construction FAILURE
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: t...@corp.fr
> Notifying upstream projects of job completion
> Finished: FAILURE
> {noformat}
> {quote}
> I didn't put that issue as BLOCKER since the solution is to recreate the job
> as freestyle one. But it's an awkward solution.
> PS : yes, I know the feature is still said to be beta.
> Cheers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
