Jenkins Failure for initial Build

553 views
Skip to first unread message

Sridhar Babu

unread,
Nov 26, 2017, 7:32:51 AM11/26/17
to Jenkins Users
Hi I am new to Jenkins and started Learning and for my trail getting below Failure message.
Could you please tell me what could be the issue

Building in workspace C:\Program Files (x86)\Jenkins\workspace\atmosphere
 > C:\Program Files\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\bin\git.exe config remote.origin.url https://github.com/g0t4/jenkins2-course-spring-boot.git # timeout=10
Fetching upstream changes from https://github.com/g0t4/jenkins2-course-spring-boot.git
 > C:\Program Files\Git\bin\git.exe --version # timeout=10
 > C:\Program Files\Git\bin\git.exe fetch --tags --progress https://github.com/g0t4/jenkins2-course-spring-boot.git +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
 > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
Checking out Revision 4bde91e33e2860b2aab142028c04eff37b7791f2 (refs/remotes/origin/master)
 > C:\Program Files\Git\bin\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\bin\git.exe checkout -f 4bde91e33e2860b2aab142028c04eff37b7791f2
Commit message: "Adding in jacoco code coverage"
 > C:\Program Files\Git\bin\git.exe rev-list 4bde91e33e2860b2aab142028c04eff37b7791f2 # timeout=10
[atmosphere] $ cmd.exe /C "mvn -f spring-boot-samples/spring-boot-sample-atmosphere/pom.xml compile && exit %%ERRORLEVEL%%"
\Jenkins\workspace\atmosphere\spring-boot-samples\spring-boot-sample-atmosphere was unexpected at this time.
Build step 'Invoke top-level Maven targets' marked build as failure
Finished: FAILURE

Victor Martinez

unread,
Nov 26, 2017, 12:18:54 PM11/26/17
to Jenkins Users
That particular error message doesn't provide enough details though, and it might be related to some environmental issue or something else, therefore I'd suggest to use some maven flags to detect what's the real error underneath:

-e, --errors
Produce execution error messages
-X, --debug
Produce execution debug output

Further details:

Cheers

H4ckSt4r

unread,
Jan 15, 2018, 1:29:36 AM1/15/18
to jenkins...@googlegroups.com

Cuong Tran

unread,
Jan 16, 2018, 7:57:31 PM1/16/18
to Jenkins Users
It looks like the project you referenced in the job doesn't exist.
Reply all
Reply to author
Forward
0 new messages