Mailinglist Archive: yast-devel (61 mails)

< Previous Next >
Re: [yast-devel] Re: [yast-commit] Build failed in Jenkins: yast-skelcd-control-SLED-SLE-12-GA #625
On Fri, 3 Oct 2014 17:05:09 +0200
Martin Vidner <mvidner@xxxxxxx> wrote:

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.


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@xxxxxxx wrote:

Started by an SCM change
Building remotely on yast-head in workspace
Checkout:yast-skelcd-control-SLED-SLE-12-GA /
<> -
hudson.remoting.Channel@4cc4f985:yast-head Using strategy: Default
Checkout:yast-skelcd-control-SLED-SLE-12-GA /
<> -
hudson.remoting.LocalChannel@4bbf48f0 Cloning the remote Git
repository Cloning repository origin ERROR: Error cloning remote
repo 'origin' : Could not clone ERROR: Cause:
Error performing command: git clone --progress -o origin
Command "git clone --progress -o origin
returned status code 128: Cloning into
fatal: could not read Username for '': 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(
at hudson.plugins.git.GitSCM$2.invoke(
hudson.FilePath$ at
hudson.remoting.UserRequest.perform( at
hudson.remoting.UserRequest.perform( at
hudson.remoting.Request$ at
at at
at -- To unsubscribe, e-mail:
yast-commit+unsubscribe@xxxxxxxxxxxx For additional commands,
e-mail: yast-commit+help@xxxxxxxxxxxx

< Previous Next >