[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Could we enable Travis-CI on our github mirrors?
From:       Elvis Angelaccio <elvis.angelaccio () kdemail ! net>
Date:       2016-04-20 16:42:31
Message-ID: CALN1cnvaz74oe0Vqz_bT_kdfjdtp4Rcfc=Aatw5g9SS2SDtFLg () mail ! gmail ! com
[Download RAW message or body]

Hi,
as many of you already know, KDE has a github mirror in place at [1].
I've been playing with travis-ci [2] and I was surprised by how easy to use
and how well integrated with github is.

I think it would be nice to have travis builds for the (mirrored)
repositories that provides a .travis.yml configuration file. The builds
would run on the travis servers, so no additional overload on the KDE
infrastructure. There is also virtually nothing to do for KDE sysadmins.
The project's maintainer is the one in charge to setup the travis
configuration file (if he wants to), in order to have working builds.

Would this be possible from a technical p.o.v.? I think the KDE github
account would have to register on the travis website and "sync" its github
repositories - that's what I had to do with my personal github account.

The use cases could be many. For example, on travis I can install optional
dependencies that are not available on our Jenkins installation. More
details in this post [3].


What do you think?

Regards,
Elvis


[1]: https://github.com/KDE
[2]: https://travis-ci.org/
[3]:
http://www.aelog.org/travis-ci-builds-of-kde-projects-on-archlinux-chroot/

[Attachment #3 (text/html)]

<div dir="ltr"><div><div><div><div><div><div>Hi,<br></div>as many of you already \
know, KDE has a github mirror in place at [1].<br></div>I&#39;ve been playing with \
travis-ci [2] and I was surprised by how easy to use and how well integrated with \
github is.<br><br>I think it would be nice to have travis builds for the (mirrored) \
repositories that provides a .travis.yml configuration file. The builds would run on \
the travis servers, so no additional overload on the KDE infrastructure. There is \
also virtually nothing to do for KDE sysadmins. The project&#39;s maintainer is the \
one in charge to setup the travis configuration file (if he wants to), in order to \
have working builds.<br><br></div><div>Would this be possible from a technical \
p.o.v.? I think the KDE github account would have to register on the travis website \
and &quot;sync&quot; its github repositories - that&#39;s what I had to do with my \
personal github account.<br></div><div><br></div>The use cases could be many. For \
example, on travis I can install optional dependencies that are not available on our \
Jenkins installation. More details in this post [3].<br><br><br></div>What do you \
think?<br><br></div>Regards,<br></div><div>Elvis<br></div><div><div><div><div><div><br><br>[1]: \
<a href="https://github.com/KDE" target="_blank">https://github.com/KDE</a><br>[2]: \
<a href="https://travis-ci.org/" target="_blank">https://travis-ci.org/</a><br>[3]: \
<a href="http://www.aelog.org/travis-ci-builds-of-kde-projects-on-archlinux-chroot/">h \
ttp://www.aelog.org/travis-ci-builds-of-kde-projects-on-archlinux-chroot/</a><br></div></div></div></div></div></div>




[prev in list] [next in list] [prev in thread] [next in thread]