eclipse - "No such file:" error in jenkins when integrating with Maven build -

-

i have started using jenkins ci tool maven selenium automation project.

the path of local eclipse workspace is:

/media/user/data/automation_scripts

and complete path of pom.xml file used execute project is: 

/media/user/data/automation_scripts/[project_name]/pom.xml

now, have installed jenkins , added maven project it. when try enter path project's pom.xml file in 'root pom' text field under 'build' following error:

no such file: ‘/media/user/data/automation_scripts/test/pom.xml’

error_message_section

whereas if navigate same path pom.xml file present. when build maven project in jenkins, following error shown:

started user test building in workspace /var/lib/jenkins/jobs/test/workspace parsing poms error: no such file /media/user/data/automation_scripts/test/pom.xml perhaps need specify correct pom file path in project configuration? finished: failure

update:

i created pom.xml file in jenkins workspace located at:

/var/lib/jenkins/jobs/test/workspace

in pom file have given path of actual pom.xml (which located in folder) in following way:

<project xmlns="http://maven.apache.org/pom/4.0.0" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xsi:schemalocation="http://maven.apache.org/pom/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">   <modelversion>4.0.0</modelversion> <name>maven default project</name> <artifactid>jenkins_test</artifactid>    <parent> <groupid>ca.test</groupid>   <artifactid>maven_test</artifactid>   <version>0.0.1-snapshot</version>   <relativepath>/media/user/data/automation_scripts/test/pom.xml</relativepath>  </parent> </project>


still getting following error now:

building in workspace /var/lib/jenkins/jobs/test/workspace parsing poms error: failed parse poms org.apache.maven.project.projectbuildingexception: problems encountered while processing poms: [fatal] non-resolvable parent pom: not find artifact ca.test:maven_test:pom:0.0.1-snapshot , 'parent.relativepath' points @ wrong local pom @ line 6, column 9  @ org.apache.maven.project.defaultprojectbuilder.build(defaultprojectbuilder.java:364) @ hudson.maven.mavenembedder.buildprojects(mavenembedder.java:361) @ hudson.maven.mavenembedder.readprojects(mavenembedder.java:331) @ hudson.maven.mavenmodulesetbuild$pomparser.invoke(mavenmodulesetbuild.java:1301) @ hudson.maven.mavenmodulesetbuild$pomparser.invoke(mavenmodulesetbuild.java:1098) @ hudson.filepath.act(filepath.java:1018) @ hudson.filepath.act(filepath.java:996) @ hudson.maven.mavenmodulesetbuild$mavenmodulesetbuildexecution.parsepoms(mavenmodulesetbuild.java:960) @ hudson.maven.mavenmodulesetbuild$mavenmodulesetbuildexecution.dorun(mavenmodulesetbuild.java:679) @ hudson.model.abstractbuild$abstractbuildexecution.run(abstractbuild.java:534) @ hudson.model.run.execute(run.java:1720) @ hudson.maven.mavenmodulesetbuild.run(mavenmodulesetbuild.java:531) @ hudson.model.resourcecontroller.execute(resourcecontroller.java:98) @ hudson.model.executor.run(executor.java:404) finished: failure

i guess there wrong relative path. can tell me missing here?

try providing relative path instead of actual absolute path. default jenkins job considers path workspace path. make pom.xml available in workspace of job , provide path file name i.e pom.xml


Comments

Post a Comment

Popular posts from this blog

sql - invalid in the select list because it is not contained in either an aggregate function -

-
i can't figure out rewrite sql statement avoid error below msg 8120, level 16, state 1, line 26 column 'staffmember.staffmemberid' invalid in select list because not contained in either aggregate function or group clause. sql statment select (select [dbo].[udf_readstaffmemberbasic](sm.staffmemberid) xml path ('staffmembersummary'), root ('items'), type ), count(sm.staffmemberid) totalresults, ceiling(cast(count(sm.staffmemberid) decimal)/ @pagesize) totalpages staffmember sm inner join staffmembertoadditionalrole ar on sm.staffmemberid = ar.staffmemberid (sm.firstname '%' + @name + '%' or sm.surname '%' + @name + '%') , (@floorid null or sm.floorid = @floorid) , (@directorateid null or sm.directorateid = @directorateid) , (@additionalroleid null or ar.additionalroleid = @additionalroleid) order sm.staffmemberid offset @page * @pagesize rows fe...
Read more

Angularjs unit testing - ng-disabled not working when adding text to textarea -

-
i trying test angularjs component using karma, mocha, power-assert. have textarea , button in component, button disabled based on length of text in textarea. when run component in browser works perfectly. can't figure out how test functionality. here's bit of code. inquiryform.js function inquiryform($scope) { // plan add logic here } angular.module('myapp').component('inquiryform', { controller: inquiryform, controlleras: 'inquiryform', templateurl: 'inquiryform.html' }); inquiryform.html <div class="contact"> <div>thanks contacting us.</div> <form> <textarea ng-model="inquiryform.inquirytext" name=""></textarea> <input type="submit" value="send" ng-disabled="!inquiryform.inquirytext.length"> </form> </div> inquiryformtest.js describe('inquiry form ', () => { let $r...
Read more

How to start daemon on android by adb -

-
can me please, head swollen... i trying run daemon on android emu/device command: adb -s <device_name> shell su -c /dir/daemon <port_number> but nothink happens, , no errors! if do: adb -s <device> shell and form shell cmdline: su -c /dir/daemon <port_number> than work fine. try use shell-script , run: adb -s <device_name> shell sh su -c /dir/script.sh <port_number> and try generate script qt code port number , use: adb -s <device_name> shell sh su -c /dir/script.sh but not helped... problem if enter adb shell previous run daemon - work. problem on different device/emu/iso_image different command format not work. example: adb -s <device_name> shell su -c /dir/daemon <port_number> // work @ emu, not @ iso and vice: adb -s <device_name> shell su -c "/dir/daemon <port_number>" // work @ iso etc. everybody can answer what's matter? sorry english adb shell su -c ...
Read more