July 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] obs-worker - restarting services in chroot env at build time
by Florian Kabus 16 Jul '12

16 Jul '12

Hi, we have an private OBS installation here (now seperated in an obs-server and one worker, both running in seperated VMs on a vSphere Server). Some of our RPMs restart services like apache or mysql in the %post directive. The problem here is that the obs-worker starts the specified services in its chroot environment but doesn't stop them after the build has completed. So all further builds fail, because the services are still running. I would expect that the worker cleans up his build environment inclusive the started services etc. But maybe I´m a bit puzzled with the underlying 'principles'. It would be nice if someone could push me in the right direction or give some best practices for a solution to this scenario. Would be a 'KVM build envorinment' be a appropriate solution for this (like build.opensuse.org does it? - As long as I interpreted the build logs correctly...) ? But I think this is probably not possible, because the appliances are already running as VMs with no HW virtualization available. Greetings Florian -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Compression format for images build
by Xin Wang 15 Jul '12

15 Jul '12

Hi all, When I'm trying to uncompress images built by OBS (e.g. [1]) in Windows, 7-Zip, PeaZip and WinRAR all fails. 7-Zip just failed to recognize the tar ball, and WinRAR complained with message 'sparse file is not supported'. After some searching, I find this bug report for 7-Zip[2]. It seems that sparse tar package is not supported in 7-Zip either. I saw from here[3] that image compressing method is hard coded in build_kiwi.sh, and using '-S' option for tar cmd. Can this option be controlled by project config? So that appliances which with Windows users as one of main audiances can be more friendly (I'm buiding one now). It will be inconvenient if users have to use GNUWin[4] or Cygwin tools to uncompress the image, especially for non-tech ones. Best Regards, [1] http://download.opensuse.org/repositories/openSUSE:/Tools/images/obs-server… [2] http://sourceforge.net/tracker/?func=detail&aid=3116688&group_id=14481&atid… [3] https://github.com/openSUSE/obs-build/blob/master/build_kiwi.sh [4] http://gnuwin32.sourceforge.net/packages/libarchive.htm -- Xin Wang (http://dram.me/) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] osc checkout fails with Content-Length is not matching file size
by He Zhenxing 14 Jul '12

14 Jul '12

Hi, I have setup an OBS server locally, when using osc to checkout packages, it would fails randomly with error Content-Length is not matching file size. If the package contains hundreds of files, it would fail always at some place and there is no way to check it out. I have encounter this error with OBS 2.0/2.1 and now 2.3 with lighttpd. I searched the mail list archive and got this: http://lists.opensuse.org/opensuse-buildservice/2011-10/msg00174.html I follow the suggestion and switched to apache2, there would be no error, but the files checked out are not correct, some files are incorrectly empty, which I think is even worse than using lighttpd. Any help would be appreciated! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] [PATCH] [backend] add "hostarch" to buildinfo if present in buildconfig
by Marcus Huewe 14 Jul '12

14 Jul '12

Hi, I just wrote a small patch which adds the hostarch to the buildinfo if it is present in the buildconfig. Currently osc also has some codepaths which check for a hostarch element (but it was never added to the buildinfo). Marcus --- src/backend/bs_repserver | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/backend/bs_repserver b/src/backend/bs_repserver index 0f20f11..e06b1f9 100755 --- a/src/backend/bs_repserver +++ b/src/backend/bs_repserver @@ -2100,6 +2100,7 @@ sub getbuildinfo { $ret->{'package'} = $packid if defined $packid; $ret->{'downloadurl'} = $BSConfig::repodownload if defined $BSConfig::repodownload;; $ret->{'arch'} = $arch; + $ret->{'hostarch'} = $bconf->{'hostarch'} if $bconf->{'hostarch'}; $ret->{'path'} = $repo->{'path'} || []; my @prp = map {"$_->{'project'}/$_->{'repository'}"} @{$repo->{'path'} || []}; if ($packtype eq 'kiwi') { -- 1.7.3.4 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

RE: [opensuse-buildservice] obs-worker-pxe.x86_64-2.3.2 setup
by Rick Liu 12 Jul '12

12 Jul '12

> > However after system configs, > > the system reboot, > > but the system doesn't come up and stays blank. [Rick Liu] Ok, I found I missed md5 file for the image from atftp.log: atftpd[2207.140179276822272]: File /local/opensuse/pxe/image/obs-worker-pxe.x86_64-2.3.2-2.3.2.md5 not found However, After I fixed md5 file issue, there's new problem. When lack of md5 file, the initialization will complete and system reboots. eg. [ 43.343600] sd 2:0:0:0: [sda] Cache data unavailable [ 43.350790] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 43.354902] sda: sda1 sda2 sda3 sda4 [ 166.632341] md: stopping all md devices. Machine reboot However, after add the md5 file (obs-worker-pxe.x86_64-2.3.2-2.3.2.md5), it just hangs at: [ 43.842498] sd 2:0:0:0: [sda] Cache data unavailable [ 43.850312] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 43.860281] sda: sda1 sda2 sda3 sda4 >From atftp.log, I can see atftp tring to transfer "image/obs-worker-pxe.x86_64-2.3.2.gz" file, but stuck at <block: 25>. (I have also increased time-out to 60s) Because of atftp time out, I also tried changing kiwiservertype from tftp to http (kiwiservertype=http) in pxelinux.cfg/default, but HTTP seems the same (timed out). aftp.log: Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: Creating new socket: 10.136.18.115:51616 Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: Serving image/obs-worker-pxe.x86_64-2.3.2.gz to 10.136.18.169:54532 Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received RRQ <filename: image/obs-worker-pxe.x86_64-2.3.2.gz, mode: octet, tsize: 0, blksize: 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: tsize option -> 193513532 Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: blksize option -> 4096 Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent OACK <tsize: 193513532, blksize: 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 0> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 1, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 1> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 2, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 2> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 3, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 3> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 4, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 4> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 5, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 5> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 6, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 6> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 7, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 7> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 8, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 8> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 9, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 9> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 10, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 10> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 11, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 11> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 12, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 12> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 13, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 13> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 14, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 14> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 15, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 15> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 16, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 16> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 17, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 17> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 18, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 18> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 19, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 19> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 20, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 20> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 21, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 21> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 22, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 22> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 23, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 23> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 24, size 4096> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: received ACK <block: 24> Jul 12 13:15:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 25, size 4096> Jul 12 13:16:01 map-build-vm-01 atftpd[13919.140229097764608]: timeout: retrying... Jul 12 13:16:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 25, size 4096> Jul 12 13:17:01 map-build-vm-01 atftpd[13919.140229097764608]: timeout: retrying... Jul 12 13:17:01 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 25, size 4096> Jul 12 13:18:02 map-build-vm-01 atftpd[13919.140229097764608]: timeout: retrying... Jul 12 13:18:02 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 25, size 4096> Jul 12 13:19:02 map-build-vm-01 atftpd[13919.140229097764608]: timeout: retrying... Jul 12 13:19:02 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 25, size 4096> Jul 12 13:20:02 map-build-vm-01 atftpd[13919.140229097764608]: timeout: retrying... Jul 12 13:20:02 map-build-vm-01 atftpd[13919.140229097764608]: sent DATA <block: 25, size 4096> Jul 12 13:21:02 map-build-vm-01 atftpd[13919.140229097764608]: client (10.136.18.169) not responding Jul 12 13:21:02 map-build-vm-01 atftpd[13919.140229097764608]: End of transfer Jul 12 13:21:02 map-build-vm-01 atftpd[13919.140229097764608]: Server thread exiting /var/log/apache2/access_log: 10.136.18.169 - - [12/Jul/2012:13:53:44 -0700] "GET /KIWI/config.00%3a0C%3a29%3a40%3a09%3aF4 HTTP/1.1" 200 223 "-" "curl/7.22.0 (x86_64-unknown-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.0e zlib/1.2.5 c-ares/1.7.5 libidn/1.22 libssh2/1.2.9" 10.136.18.169 - - [12/Jul/2012:13:54:18 -0700] "GET /image/obs-worker-pxe.x86_64-2.3.2.md5 HTTP/1.1" 200 59 "-" "curl/7.22.0 (x86_64-unknown-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.0e zlib/1.2.5 c-ares/1.7.5 libidn/1.22 libssh2/1.2.9" 10.136.18.169 - - [12/Jul/2012:13:54:21 -0700] "GET /image/obs-worker-pxe.x86_64-2.3.2.md5 HTTP/1.1" 200 59 "-" "curl/7.22.0 (x86_64-unknown-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.0e zlib/1.2.5 c-ares/1.7.5 libidn/1.22 libssh2/1.2.9" 10.136.18.169 - - [12/Jul/2012:13:54:22 -0700] "GET /image/obs-worker-pxe.x86_64-2.3.2.gz HTTP/1.1" 200 193513532 "-" "curl/7.22.0 (x86_64-unknown-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.0e zlib/1.2.5 c-ares/1.7.5 libidn/1.22 libssh2/1.2.9" /var/log/apache2/error_log: [Thu Jul 12 13:59:22 2012] [info] [client 10.136.18.169] (70007)The timeout specified has expired: core_output_filter: writing data to the network

1 0

RE: [opensuse-buildservice] obs-worker-pxe.x86_64-2.3.2 setup
by Rick Liu 12 Jul '12

12 Jul '12

> > > I downloaded obs-worker-pxe.x86_64-2.3.2-Build13.6-pxe.tar.bz2 > > > and try to PXE deploy the obs-worker. > > > > > > During PXE boot, > > > I can see it copied boot/initrd and boot/linux > > > and start system configs. > > > > > > However after system configs, > > > the system reboot, > > > but the system doesn't come up and stays blank. > > > > What does that mean? the kernel is loading, but black > > screen during initialization? => try "nomodeset=1" as kernel > parameter. > > [Rick Liu] I added "nomodeset=1" right after "append initrd=boot/initrd" in pxelinux.cfg/default but the result is the same: /dev/sda is partitioned without format file system or mount point. # cat pxelinux.cfg/default DEFAULT KIWI-Boot LABEL KIWI-Boot kernel boot/linux # append initrd=boot/initrd vga=normal ramdisk_size=512000 ramdisk_blocksize=4096 kiwiserver=10.136.18.115 append initrd=boot/initrd nomodeset=1 vga=normal kiwiserver=10.136.18.115 kiwiservertype=tftp console=tty0 console=ttyS0,115200 IPAPPEND 2 > [Rick Liu] > After loading kernel and initrd, > the system starts initialization. > At the end of initialization, > the machine reboots. > > [Attach: initialization.jpg (initialization screen shot)] > > After the machine reboot, > the system doesn't come up. > I use a openSUSE Gnome Live CD to boot, > and can see that the /dev/sda has been partitioned as below: > > # fdisk -l /dev/sda > > Disk /dev/sda: 107.4 GB, 107374182400 bytes > 255 heads, 63 sectors/track, 13054 cylinders, total 209715200 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00004c6f > > Device Boot Start End Blocks Id System > /dev/sda1 2048 2056319 1027136 82 Linux swap / > Solaris > /dev/sda2 2056320 43006004 20474842+ 83 Linux > /dev/sda3 43006008 83955690 20474841+ 83 Linux > /dev/sda4 83955696 209712509 62878407 8e Linux LVM > > But no format partition nor mount partition. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

RE: [opensuse-buildservice] obs-worker-pxe.x86_64-2.3.2 setup
by Rick Liu 12 Jul '12

12 Jul '12

> > I downloaded obs-worker-pxe.x86_64-2.3.2-Build13.6-pxe.tar.bz2 > > and try to PXE deploy the obs-worker. > > > > During PXE boot, > > I can see it copied boot/initrd and boot/linux > > and start system configs. > > > > However after system configs, > > the system reboot, > > but the system doesn't come up and stays blank. > > What does that mean? the kernel is loading, but black > screen during initialization? => try "nomodeset=1" as kernel parameter. > [Rick Liu] After loading kernel and initrd, the system starts initialization. At the end of initialization, the machine reboots. [Attach: initialization.jpg (initialization screen shot)] After the machine reboot, the system doesn't come up. I use a openSUSE Gnome Live CD to boot, and can see that the /dev/sda has been partitioned as below: # fdisk -l /dev/sda Disk /dev/sda: 107.4 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders, total 209715200 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00004c6f Device Boot Start End Blocks Id System /dev/sda1 2048 2056319 1027136 82 Linux swap / Solaris /dev/sda2 2056320 43006004 20474842+ 83 Linux /dev/sda3 43006008 83955690 20474841+ 83 Linux /dev/sda4 83955696 209712509 62878407 8e Linux LVM But no format partition nor mount partition.

1 0

[opensuse-buildservice] obs-worker-pxe.x86_64-2.3.2 setup
by Rick Liu 12 Jul '12

12 Jul '12

Hi, I downloaded obs-worker-pxe.x86_64-2.3.2-Build13.6-pxe.tar.bz2 and try to PXE deploy the obs-worker. During PXE boot, I can see it copied boot/initrd and boot/linux and start system configs. However after system configs, the system reboot, but the system doesn't come up and stays blank. Did I miss any setup or have wrong config? Thanks, Rick The PXE client has 100GB disk (/dev/sda). Below is my configs on PXE server: PXE server IP: 10.136.18.115 OS: openSUSE 12.1 x86_64 # cat pxelinux.cfg/default DEFAULT KIWI-Boot LABEL KIWI-Boot kernel boot/linux #append initrd=boot/initrd vga=normal ramdisk_size=512000 ramdisk_blocksize=4096 kiwiserver=10.136.18.115 append initrd=boot/initrd vga=normal kiwiserver=10.136.18.115 kiwiservertype=tftp console=tty0 console=ttyS0,115200 IPAPPEND 2 # cat KIWI/config.00:0C:29:40:09:F4 IMAGE=/dev/sda2;obs-worker-pxe.x86_64-2.3.2;2.3.2;10.136.18.115;4096;compressed CONF=/KIWI/COLFAX.16fach/buildhost.config;/etc/buildhost.config;10.136.18.115;4096 PART=1000;S;x,20000;L;/,20000;L;/abuild.cache,x;8e; DISK=/dev/sda I installed "kiwi-pxeboot- 5.03.16-491.4" for my PXE boot structure: /srv/tftpboot/ # ls -l * -rw-r--r-- 1 root root 346 Jul 11 13:49 README -rwxr-xr-x 1 root root 34524 Jul 11 13:49 mboot.c32 -rwxr-xr-x 1 root root 26535 Jul 11 13:49 pxelinux.0 KIWI: total 4 -rw-r--r-- 1 root root 229 Jul 11 14:46 config.00:0C:29:40:09:F4 boot: total 52492 lrwxrwxrwx 1 root root 47 Jul 11 14:36 initrd -> initrd-netboot-suse-12.1.x86_64-2.1.1.splash.gz -rw-r--r-- 1 root root 4715760 Jul 11 14:29 initrd-netboot-suse-12.1.x86_64-2.1.1.kernel.3.1.10-1.16-default -rw-r--r-- 1 root root 49026405 Jul 11 14:28 initrd-netboot-suse-12.1.x86_64-2.1.1.splash.gz lrwxrwxrwx 1 root root 64 Jul 11 16:15 linux -> initrd-netboot-suse-12.1.x86_64-2.1.1.kernel.3.1.10-1.16-default image: total 1159740 -rw-r--r-- 1 root root 994050049 Jul 11 14:18 obs-worker-pxe.x86_64-2.3.2 lrwxrwxrwx 1 root root 30 Jul 11 14:47 obs-worker-pxe.x86_64-2.3.2.ext4 -> obs-worker-pxe.x86_64-2.3.2.gz -rw-r--r-- 1 root root 193513532 Jul 11 14:33 obs-worker-pxe.x86_64-2.3.2.gz pxelinux.cfg: total 8 -rw-r--r-- 1 root root 322 Jul 11 16:25 default -rw-r--r-- 1 root root 204 Jul 11 13:49 default.default upload: total 0 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Groups Files
by Jamie Lennox 12 Jul '12

12 Jul '12

Hi, Is there any way to add a groups file into an OBS repo (createrepo -g comps.xml) ? I'm running a standalone instance but i imagine it's relevant to build.opensuse as well. I had a quick look through bs_publish and i didn't see anything but it wasn't extensive. I don't expect OBS to generate this file, i have one already but is there anyway to get it into the service? Thanks, Jamie -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] make use of travis-ci.org
by Stephan Kulow 11 Jul '12

11 Jul '12

Hi, If you merged openSUSE/open-build-service into your github fork, you can now enable the service hook "travis ci" and have it run our test suite for you. To do that, go to your fork, and click "Admin", then "Service Hooks", scroll down to "Travis" and then scroll up again to follow the instructions that appear on the right column (of course if you have a very large screen, you don't have to scroll :) Note, that we may require this to be enabled for merging pull requests (of course just as we require decent test coverage ;) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0