[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-11-15 Thread s.x...@sta.samsung.com (JIRA)














































Sam Xiao
 commented on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds















I have the same problem with Gerrit's SSH URL



11:04:53 Building remotely on bob-10.47 in workspace /home/jenkins/slave-root/workspace/gerrit_client_android_build_debug
11:04:53 
11:04:53 Deleting project workspace... done
11:04:53 
11:04:53 Cloning the remote Git repository
11:04:53 Cloning repository ssh://XX:29418/client.git
11:04:53 git --version
11:04:53 git version 1.8.4.2
11:05:15 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.



Here suggest a downgrade:
https://groups.google.com/forum/#!topic/repo-discuss/BWjtSX07IpQ



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-11-15 Thread s.x...@sta.samsung.com (JIRA)














































Sam Xiao
 updated  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
















Change By:


Sam Xiao
(15/Nov/13 7:37 PM)




Priority:


Major
Blocker





Component/s:


ssh-credentials



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-11-26 Thread kcbu...@gmail.com (JIRA)














































Kevin Burge
 commented on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds















I'm running in to the same issue.  This doesn't prevent checkout, it just causes Jenkins to clear the workspace so that my build completely starts over, which can take 45 minutes, when it could take 1 or 2.  This is a significant problem for us.  I'd rather not downgrade as I would have to reconfigure many jobs to specify the ref location (like I did when I upgraded from the older git client).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-11-26 Thread kcbu...@gmail.com (JIRA)












































  
Kevin Burge
 edited a comment on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
















I'm running in to the same issue (integration with Gerrit Trigger).  This doesn't prevent checkout, it just causes Jenkins to clear the workspace so that my build completely starts over, which can take 45 minutes, when it could take 1 or 2.  This is a significant problem for us.  I'd rather not downgrade as I would have to reconfigure many jobs to specify the ref location (like I did when I upgraded from the older git client).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-11-26 Thread kcbu...@gmail.com (JIRA)












































  
Kevin Burge
 edited a comment on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
















I'm running in to the same issue (integration with Gerrit Trigger).  This doesn't prevent checkout, it just causes Jenkins to clear the workspace so that my build completely starts over, which can take 45 minutes, when it could take 1 or 2.  This is a significant problem for us.  I'd rather not downgrade as I would have to reconfigure many jobs to specify the ref location (like I did when I upgraded from the older git client).

Fetching changes from the remote Git repository
Fetching upstream changes from git://repo.dev.systemware.com/xds
Checking out Revision 407f296d95c4626e65647e50573f6a2ad08b0eef (master)
ERROR: Unable to retrieve changeset
hudson.plugins.git.GitException: Failed to find parent id. 
	at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getFirstParent(GerritTriggerBuildChooser.java:156)
	at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.prevBuildForChangelog(GerritTriggerBuildChooser.java:117)
	at hudson.plugins.git.GitSCM.computeChangeLog(GitSCM.java:935)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:875)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1376)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:655)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560)
	at hudson.model.Run.execute(Run.java:1592)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Caused by: java.lang.UnsupportedOperationException
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl.getRepository(RemoteGitImpl.java:187)
	at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getFirstParent(GerritTriggerBuildChooser.java:146)
	... 11 more
Cleaning workspace



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-12-11 Thread rgrigor...@gmail.com (JIRA)














































Roman G
 commented on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds















I observe the stacktrace  but in same time correct hash was checkout from gerrit
I checked sources and see that it happens  getFirstParent function.
Looks like this functionality touch only changelog but not. I could assume that 
it happens because gerrit patchsets are placed in detached head and parent commit cannot 
be simple found



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2013-12-11 Thread rgrigor...@gmail.com (JIRA)












































  
Roman G
 edited a comment on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
















I observe the stacktrace  but in same time correct hash was checkout from gerrit
I checked sources and see that it happens  getFirstParent function.
Looks like this functionality touch only changelog but not code checkout. I could assume that 
it happens because gerrit patchsets are placed in detached head and parent commit cannot 
be simple found



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2014-01-02 Thread leevar.willi...@gmail.com (JIRA)














































Leevar Williams
 commented on  JENKINS-20243


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds















This seems to be caused by JENKINS-20098, and fixed by https://github.com/jenkinsci/gerrit-trigger-plugin/commit/599cea84849432d3e12f427237025680e8276dce.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2014-02-08 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 closed  JENKINS-20243 as Fixed


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
















Change By:


Mark Waite
(08/Feb/14 2:18 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds

2014-02-08 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 resolved  JENKINS-20243 as Fixed


Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
















Since Leevar reports it is fixed by a change to the gerrit-trigger plugin, this issue is resolved.





Change By:


Mark Waite
(08/Feb/14 2:17 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.