[yast-devel] Re: [yast-commit] Build failed in Jenkins: yast-skelcd-control-SLED-SLE-12-GA #625
This one, and its SLES buddy, has been flooding the yast-commit list, so I have disabled it before we agree how to fix it. I think the way to fix it is actually to create the SLE-12-GA branch for the skelcd-control-SLE[DS] packages. Then we can also fix all the other failures which complain that either the package does not exist in Devel:YaST:SLE-12 or the target project for SR does not exist. (use just osc:commit) On Fri, Oct 03, 2014 at 04:51:23PM +0200, hudson@suse.de wrote:
See http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/625/
------------------------------------------ Started by an SCM change Building remotely on yast-head in workspace http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ Checkout:yast-skelcd-control-SLED-SLE-12-GA / http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ - hudson.remoting.Channel@4cc4f985:yast-head Using strategy: Default Checkout:yast-skelcd-control-SLED-SLE-12-GA / http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ - hudson.remoting.LocalChannel@4bbf48f0 Cloning the remote Git repository Cloning repository origin ERROR: Error cloning remote repo 'origin' : Could not clone https://github.com/yast/yast-skelcd-control-SLED.git ERROR: Cause: Error performing command: git clone --progress -o origin https://github.com/yast/yast-skelcd-control-SLED.git http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ Command "git clone --progress -o origin https://github.com/yast/yast-skelcd-control-SLED.git http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/" returned status code 128: Cloning into 'http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/'... fatal: could not read Username for 'https://github.com': No such device or address
Trying next repository ERROR: Could not clone repository FATAL: Could not clone hudson.plugins.git.GitException: Could not clone at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:977) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:908) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) -- To unsubscribe, e-mail: yast-commit+unsubscribe@opensuse.org For additional commands, e-mail: yast-commit+help@opensuse.org
-- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On Fri, 3 Oct 2014 17:05:09 +0200
Martin Vidner
This one, and its SLES buddy, has been flooding the yast-commit list, so I have disabled it before we agree how to fix it.
I think the way to fix it is actually to create the SLE-12-GA branch for the skelcd-control-SLE[DS] packages.
Problem is this case is that our global jenkins handling tools do expect yast-prefix. As you can see it failed as it try invalid name of this git clone. I can handle it for now. Josef
Then we can also fix all the other failures which complain that either the package does not exist in Devel:YaST:SLE-12 or the target project for SR does not exist. (use just osc:commit)
On Fri, Oct 03, 2014 at 04:51:23PM +0200, hudson@suse.de wrote:
See http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/625/
------------------------------------------ Started by an SCM change Building remotely on yast-head in workspace http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ Checkout:yast-skelcd-control-SLED-SLE-12-GA / http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ - hudson.remoting.Channel@4cc4f985:yast-head Using strategy: Default Checkout:yast-skelcd-control-SLED-SLE-12-GA / http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ - hudson.remoting.LocalChannel@4bbf48f0 Cloning the remote Git repository Cloning repository origin ERROR: Error cloning remote repo 'origin' : Could not clone https://github.com/yast/yast-skelcd-control-SLED.git ERROR: Cause: Error performing command: git clone --progress -o origin https://github.com/yast/yast-skelcd-control-SLED.git http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/ Command "git clone --progress -o origin https://github.com/yast/yast-skelcd-control-SLED.git http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/" returned status code 128: Cloning into 'http://river.suse.de/job/yast-skelcd-control-SLED-SLE-12-GA/ws/'... fatal: could not read Username for 'https://github.com': No such device or address
Trying next repository ERROR: Could not clone repository FATAL: Could not clone hudson.plugins.git.GitException: Could not clone at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:977) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:908) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) -- To unsubscribe, e-mail: yast-commit+unsubscribe@opensuse.org For additional commands, e-mail: yast-commit+help@opensuse.org
participants (2)
-
Josef Reidinger -
Martin Vidner