Mailinglist Archive: yast-commit (1997 mails)

< Previous Next >
[yast-commit] Build failed in Jenkins: yast-storage-ng-master #531
  • From: admin@xxxxxxxxxxxx
  • Date: Mon, 23 Apr 2018 10:08:57 +0000 (UTC)
  • Message-id: <334868927.3.1524478137520.JavaMail.jenkins@ci-opensuse>
See
<http://ci.opensuse.org/job/yast-storage-ng-master/531/display/redirect?page=changes>

Changes:

[Josef Reidinger] continue submitting to SLE15 GA

------------------------------------------
Started by GitHub push by jreidinger
Started by GitHub push by jreidinger
[EnvInject] - Loading node environment variables.
Building remotely on yast-jenkins-original (yast-jenkins) in workspace
<http://ci.opensuse.org/job/yast-storage-ng-master/ws/>
git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
git config remote.origin.url https://github.com/yast/yast-storage-ng.git #
timeout=10
Fetching upstream changes from https://github.com/yast/yast-storage-ng.git
git --version # timeout=10
git fetch --tags --progress https://github.com/yast/yast-storage-ng.git
+refs/heads/*:refs/remotes/origin/*
git rev-parse origin/master^{commit} # timeout=10
Checking out Revision bbc69401a9f5ba670c0e32051c0748e7eaaa818a (origin/master)
git config core.sparsecheckout # timeout=10
git checkout -f bbc69401a9f5ba670c0e32051c0748e7eaaa818a
Commit message: "Merge pull request #614 from yast/autosubmit_ga"
git rev-list --no-walk e1ef58bbaa6c171d33e510c15db8f364f3153ba4 # timeout=10
Cleaning workspace
git rev-parse --verify HEAD # timeout=10
Resetting working tree
git reset --hard # timeout=10
git clean -fdx # timeout=10
[yast-storage-ng-master] $ /bin/sh -xe /tmp/jenkins625658403718332565.sh
+ cd <http://ci.opensuse.org/job/yast-storage-ng-master/ws/>
+ rake osc:sr
rake aborted!
Not configuration found for sle15
<http://ci.opensuse.org/job/yast-storage-ng-master/ws/Rakefile>:22:in `<top
(required)>'
LoadError: cannot load such file -- yast/rake
<http://ci.opensuse.org/job/yast-storage-ng-master/ws/Rakefile>:22:in `<top
(required)>'
(See full trace by running task with --trace)
Build step 'Execute shell' marked build as failure

< Previous Next >
This Thread
Follow Ups