[JIRA] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files

2013-03-13 Thread cra...@ieee.org (JIRA)














































Craig Newell
 created  JENKINS-17198


Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


13/Mar/13 6:10 PM



Description:


The jGIT client has lots of repository compatibility issues as compared to the normal command line git client. Updating to git-client 1.0.4 results in:

Building remotely on mac mini 1 in workspace /Users/jenkins/workspace/Fuji
Checkout:Fuji / /Users/jenkins/workspace/Fuji - hudson.remoting.Channel@c27576:mac mini 1
Using strategy: Default
Last Built Revision: Revision 88877737299f64f83e8230928e8b2db4ebe1826b (origin/master)
Fetching changes from 1 remote Git repository
Commencing build of Revision 124296a2ae55606a975ed1888c4e030dd9e0f3e4 (origin/master)
Checking out Revision 124296a2ae55606a975ed1888c4e030dd9e0f3e4 (origin/master)
FATAL: Could not checkout 124296a2ae55606a975ed1888c4e030dd9e0f3e4
hudson.plugins.git.GitException: Could not checkout 124296a2ae55606a975ed1888c4e030dd9e0f3e4
	at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68)
	at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273)
	at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57)
	at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232)
	at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:680)
Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files: 
support/tools/relink/macholib/MachO.py


whereas the normal command line git client is happy with the repository.


Can we get a work around of a configuration setting to say use either the command line git client or jGIT?




Environment:


git-client  1.0.2




Project:


Jenkins



Priority:


Blocker



Reporter:


Craig Newell

























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] (JENKINS-15578) hudson.security.AccessDeniedException2: anonymous is missing the Administer permission

2012-10-19 Thread cra...@ieee.org (JIRA)














































Craig Newell
 created  JENKINS-15578


hudson.security.AccessDeniedException2: anonymous is missing the Administer permission















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


ios-device-connector



Created:


19/Oct/12 9:38 AM



Description:


I have my Jenkins installation configured to require LDAP logins and only certain users are administrators and the rest just have read only rights. When restarting Jenkins after installing the ios-device-connector plugin, all my slaves fail to connect with the following:

ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
hudson.security.AccessDeniedException2: anonymous is missing the Administer permission
at hudson.security.ACL.checkPermission(ACL.java:54)
at hudson.model.Node.checkPermission(Node.java:393)
at org.jenkinsci.plugins.ios.connector.iOSDeviceList.update(iOSDeviceList.java:91)
at org.jenkinsci.plugins.ios.connector.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:21)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:396)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:317)
at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:454)
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:293)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)


If I allow all users administrator access, then the slaves reconnect correctly and I can see the iOS device status.




Environment:


Jenkins 1.486 on Linux x86 with Mac OS X 10.8.2 slaves




Project:


Jenkins



Priority:


Blocker



Reporter:


Craig Newell

























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