Builds for ejabberd-contrib in Ubuntu Yakkety

149 of 49 results
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on z13-010 and finished taking 5 minutes — see the log
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on z13-010 and finished taking 5 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-022 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-022 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on sagari (powerpc) and finished taking 7 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on sagari (powerpc) and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-26 and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-26 and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-026 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-026 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-034 and finished taking 4 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-034 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-51 and finished taking 6 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.08.01~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-51 and finished taking 6 minutes — see the log
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on z13-018 and finished taking 4 minutes — see the log
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on z13-018 and finished taking 4 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-019 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-019 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on denneed01 (powerpc) and finished taking 7 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on denneed01 (powerpc) and finished taking 7 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-34 and finished taking 2 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-34 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on kishi01 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on kishi01 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-015 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-015 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-30 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.06.29~dfsg0-1 in ubuntu yakkety PROPOSED
Build started on lgw01-30 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on z13-018 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on z13-018 and finished taking 3 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-023 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on bos01-ppc64el-023 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on sagari (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on sagari (powerpc) and finished taking 5 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on lgw01-59 and finished taking 3 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on lgw01-59 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on kishi16 (highbank) and finished taking 6 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on kishi16 (highbank) and finished taking 6 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-013 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on bos01-arm64-013 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on lcy01-32 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.04.11~dfsg0-2 in ubuntu yakkety PROPOSED
Build started on lcy01-32 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on z13-018 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on bos01-ppc64el-028 and finished taking 2 minutes — see the log
[FULLYBUILT] powerpc build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on sagari (powerpc) and finished taking 6 minutes — see the log
[FULLYBUILT] i386 build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on lgw01-15 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on kishi17 (highbank) and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on bos01-arm64-001 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of ejabberd-contrib 0.2016.01.12~dfsg0-1 in ubuntu xenial PROPOSED
Build started on lgw01-10 and finished taking 3 minutes — see the log
149 of 49 results