[JIRA] (JENKINS-38198) Jenkins and Maven SOA BPEL project deployment issue

6 views
Skip to first unread message

ats.sahu@gmail.com (JIRA)

unread,
Sep 14, 2016, 8:43:02 AM9/14/16
to jenkinsc...@googlegroups.com
Atul Gupta created an issue
 
Jenkins / Bug JENKINS-38198
Jenkins and Maven SOA BPEL project deployment issue
Issue Type: Bug Bug
Assignee: Oliver Gondža
Attachments: pom.xml, pom.xml
Components: jenkins-test-harness
Created: 2016/Sep/14 12:42 PM
Environment: development
Labels: jenkins plugin api configuration
Priority: Major Major
Reporter: Atul Gupta

Hi Team,

I am trying to deploy SOA BPEL project using Jenkins and Maven, but I am facing one issue here. I am not able to deploy the code using Jenkins while I am able to deploy my code using Maven.

I am getting below error message.

Please find an attachment of my POM file.

this file is present in my user/.m2/ folder. com.oracle.soa:sar-common:pom:12.2.1-0-0

Building in workspace C:\Users----\.jenkins\workspace\sca-test
Updating https://------------/svn/repos/oracleidp/BPEL/Trunk/test-soa-application at revision '2016-09-14T17:55:37.554 +0530'
At revision 232

No changes for https://-------------/svn/repos/oracleidp/BPEL/Trunk/test-soa-application since the previous build
Parsing POMs
ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Failure to find com.oracle.soa:sar-common:pom:12.2.1-0-0 in http://repo.maven.apache.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 no local POM @ line 5, column 10

at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1301)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)
at hudson.FilePath.act(FilePath.java:1018)
at hudson.FilePath.act(FilePath.java:996)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
at hudson.model.Run.execute(Run.java:1741)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

ats.sahu@gmail.com (JIRA)

unread,
Sep 15, 2016, 1:33:01 AM9/15/16
to jenkinsc...@googlegroups.com
Atul Gupta updated an issue
Change By: Atul Gupta
Labels: api configuration jenkins plugin pom

ats.sahu@gmail.com (JIRA)

unread,
Sep 15, 2016, 1:34:02 AM9/15/16
to jenkinsc...@googlegroups.com
Atul Gupta updated an issue
Change By: Atul Gupta
Labels: api configuration jenkins maven- plugin plugin pom

ats.sahu@gmail.com (JIRA)

unread,
Sep 16, 2016, 12:51:01 AM9/16/16
to jenkinsc...@googlegroups.com
Atul Gupta closed an issue as Fixed
 

Identified my issue. So closing this issue

Change By: Atul Gupta
Status: Open Closed
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages