26 Apr
2018
26 Apr
'18
11:01
See <https://ci.suse.de/job/libyui-qt-graph-sle12sp4/1/display/redirect> ------------------------------------------ Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on yast-head1 (yast-head libstorage libyui snapper) in workspace <https://ci.suse.de/job/libyui-qt-graph-sle12sp4/ws/> Cloning the remote Git repository Cloning repository https://github.com/libyui/libyui-qt-graph.git > git init <https://ci.suse.de/job/libyui-qt-graph-sle12sp4/ws/> # timeout=10 Fetching upstream changes from https://github.com/libyui/libyui-qt-graph.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/libyui/libyui-qt-graph.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/libyui/libyui-qt-graph.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/libyui/libyui-qt-graph.git # timeout=10 Fetching upstream changes from https://github.com/libyui/libyui-qt-graph.git > git fetch --tags --progress https://github.com/libyui/libyui-qt-graph.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/SLE-12-SP4^{commit} # timeout=10 Checking out Revision 48069ba9615ce14a0fc81a87f93fe414ee5b5f26 (origin/SLE-12-SP4) > git config core.sparsecheckout # timeout=10 > git checkout -f 48069ba9615ce14a0fc81a87f93fe414ee5b5f26 Commit message: "adapt Rakefile and Dockerfile for SLE-12-SP4" First time build. Skipping changelog. > git tag -a -f -m Jenkins Build #1 jenkins-libyui-qt-graph-sle12sp4-1 # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 [libyui-qt-graph-sle12sp4] $ /bin/sh -xe /tmp/jenkins3765387602032129484.sh + cd <https://ci.suse.de/job/libyui-qt-graph-sle12sp4/ws/> + rake osc:sr rake aborted! Not configuration found for sle12sp4 <https://ci.suse.de/job/libyui-qt-graph-sle12sp4/ws/Rakefile>:10:in `<top (required)>' (See full trace by running task with --trace) Build step 'Execute shell' marked build as failure