![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Praqma Support
|
|
Components:
|
config-rotator |
|
Created:
|
03/May/13 9:00 AM
|
|
Description:
|
I get the following error when CR tries to clone:
— snippet (modified to be anonymous) —
[ConfigRotator] Version: 1.1.0
[ConfigRotator] Configuration from scratch
net.praqma.jenkins.configrotator.ConfigurationRotatorException: Unable to get component for http://myrepo:8080/scm/git/project.git,
at net.praqma.jenkins.configrotator.scm.git.GitConfiguration.<init>(GitConfiguration.java:29)
at net.praqma.jenkins.configrotator.scm.git.Git$GitPerformer.getInitialConfiguration(Git.java:64)
at net.praqma.jenkins.configrotator.scm.git.Git$GitPerformer.getInitialConfiguration(Git.java:56)
at net.praqma.jenkins.configrotator.ConfigurationRotator.checkout(ConfigurationRotator.java:153)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1325)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
at hudson.model.Run.execute(Run.java:1516)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: hudson.util.IOException2: remote file operation failed: /srv/user/.jenkins/workspace/CI-UpgradeScript at hudson.remoting.Channel@1a72772:BuildHostSeven
at hudson.FilePath.act(FilePath.java:848)
at hudson.FilePath.act(FilePath.java:825)
at net.praqma.jenkins.configrotator.scm.git.GitConfiguration.<init>(GitConfiguration.java:26)
... 11 more
Caused by: java.io.IOException: org.eclipse.jgit.api.errors.TransportException: http://myrepo:8080/scm/git/project.git: not authorized
at net.praqma.jenkins.configrotator.scm.git.ResolveConfigurationComponent.invoke(ResolveConfigurationComponent.java:117)
at net.praqma.jenkins.configrotator.scm.git.ResolveConfigurationComponent.invoke(ResolveConfigurationComponent.java:25)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309)
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: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:722)
Caused by: org.eclipse.jgit.api.errors.TransportException: http://myrepo:8080/scm/git/project.git: not authorized
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:137)
at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:179)
at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:125)
at net.praqma.jenkins.configrotator.scm.git.ResolveConfigurationComponent.invoke(ResolveConfigurationComponent.java:75)
... 11 more
— snippet —
I can login on the build host, and as the user running the jenkins slave manually clone the repository.
Two thing are "special":
1) the authentification is read-only, and used git-credentials
user@buildhostseven:~$ cat .gitconfig
[credential]
helper = store
user@buildhostseven:~$ cat .git-credentials
http://user:password@myrepo%3a8080
2) Notice the port 8080
|
|
Environment:
|
Master + slave, Ubuntu Linux
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Bue Petersen
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
