Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 380426

Summary:	Hudson build has stopped working for gemini-jpa project since migrating to git
Product:	Community	Reporter:	Michael Keith <michael.keith>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	denis.roy
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Michael Keith

2012-05-23 10:59:02 EDT

Looks like the build steps are not working, since mvn or any other build step that I try doesn't get run. Could be because the clone is not working? Is there some extra step that is required to allow the Hudson build to clone the git repo? Dunno, but I just keep getting "Nothing to do":

Started by user mkeith
Building remotely on hudson-slave2
Checkout:gemini-jpa / /opt/buildhomes/hudsonBuild/workspace/gemini-jpa - hudson.remoting.Channel@5015268b:hudson-slave2
Using strategy: Default
Checkout:gemini-jpa / /opt/buildhomes/hudsonBuild/workspace/gemini-jpa - hudson.remoting.LocalChannel@424bd639
Fetching changes from the remote Git repository
Fetching upstream changes from git://git.eclipse.org/gitroot/gemini.jpa/org.eclipse.gemini.jpa.git
Nothing to do
Archiving artifacts
Sending e-mails to: michael.keith@oracle.com
[DEBUG] Skipping watched dependency update for build: gemini-jpa #39 due to result: FAILURE
Finished: FAILURE

Any suggestions?

Comment 1 Eclipse Webmaster

2012-05-25 09:32:40 EDT

Did you convert an existing job to use Git?  I'm wondering if Hudson is 'saving' the code state in some way and isn't seeing the changes in git. 

If you manually checkout the code via the shell script widget in the configure pane, does the code get checked out?

Have you tried removing the workspace?

-M.

Comment 2 Michael Keith

2012-05-28 13:09:35 EDT

Yes, it used to be checking out from svn until we converted to git. 

Yes, I have tried cleaning and even removing the workspace. Same result.

Not sure what you mean when you say the "shell script widget in the configure pane". I only know of a shell script that can be executed as a build step, but that doesn't help because the build steps are not running.

Comment 3 Eclipse Webmaster

2012-05-28 14:43:18 EDT

I think the issue may be the branch you're using.

I cloned the gemini-jpa job and removed all the extra steps, and I was getting the same 'failed to determine'.  Then I copied the jetty-rt git settings and it was much happier.  So I took a quick look here: http://git.eclipse.org/c/gemini.jpa/org.eclipse.gemini.jpa.git and set the branch to 'trunk' and then the build seemed happier.

-M.

Comment 4 Michael Keith

2012-05-28 15:22:15 EDT

Ah! Just goes to show my git ignorance. I thought trunk *was* the master. How did it fill the hudson workspace with the correct directories, then, if it was pointing to a branch that didn't have anything in it? Also, if trunk is not the master what is in the master and how come I don't see it under "branches" on the web site?

http://git.eclipse.org/c/gemini.jpa/org.eclipse.gemini.jpa.git

Comment 5 Eclipse Webmaster

2012-05-28 15:34:02 EDT

I think that 'trunk' is an SVNism, so it's most likely a result of the SVN to Git conversion.

I'm not familiar enough with the Hudson/Git internals to offer anything other than a guess that Hudson is cloning the entire repo and then branch hunting after the fact.

Have you tried 'origin/master' as the branch name?

-M.

Comment 6 Michael Keith

2012-05-28 15:58:37 EDT

I had thought the main branch was master, but now I don't think there actually even is a master branch in this repo. I think it is just the default name, but when the migration of this repo happened it probably got named "trunk" instead.

Okay, well, I think I know enough now to keep things going.

Thank you very much indeed for all your help!

-Mike

Comment 7 Denis Roy

2013-09-26 09:18:12 EDT

I think we can mark this as fixed.