Moin, I've been working on this task ($SUBJECT, https://trello.com/c/Rg7bI6rP/367-3-add-libstorage-snapper-to-jenkins) for some time and implemented a simple but ugly solution: 1. New Jenkins project: https://ci.suse.de/view/openSUSE/job/snapper/configure 2. New simple Rakefile at https://github.com/kobliha/snapper/tree/jenkins_support 3. Several newly installed packages at vm-yast-ci-worker (automake, libtool, gcc-c++, libmount-devel, dbus-1-devel, libacl-devel) 4. make -f Makefile.repo && rake osc:build This currently SUCCEEDS! :) Yast projects have .spec files in their /package directories, but snapper has snapper.spec.in and the .spec file is then generated on-the-fly. Although the current Jenkins solution is really ugly as it brings too many new dependencies into the infrastructure, it's a step forward (at least I hope so). So, what do you think of that? How bad is 'bad', how ugly is 'ugly' :)? PS: If you can't access some pieces of the infrastructure, then you just can't, and I'm sorry -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org