[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Could we enable Travis-CI on our github mirrors?
From: Elvis Angelaccio <elvis.angelaccio () kdemail ! net>
Date: 2016-04-20 21:00:26
Message-ID: CALN1cnsM88U66kYCPGgVDfHqA_qDdpeW8GBQgbpw89ozUp5hiQ () mail ! gmail ! com
[Download RAW message or body]
2016-04-20 22:09 GMT+02:00 Albert Astals Cid <aacid@kde.org>:
> El dimecres, 20 d'abril de 2016, a les 18:42:31 CEST, Elvis Angelaccio va
> escriure:
> > 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?
>
> I don't see the point in having two CI systems, just help improve the one
> we
> have.
>
> If you need dependencies, why did you start a new CI system instead of
> asking
> for the dependendies to be installed?
>
Well I did ask, but those deps are not available in the Ubuntu repositories
currently used by Jenkins.
Maybe a solution could be to install them from source/manually, but that
requires work from the sysadmins, who have already enough in their plate.
I did not start a new CI, I was basically playing with travis for fun. But
then it turned out that it could solve an issue I have. The travis
infrastrucure is already there, why not use it if one or more projects
could benefit? Seems a win-win to me.
>
> Cheers,
> Albert
>
Cheers,
Elvis
>
> >
> > 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"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-04-20 \
22:09 GMT+02:00 Albert Astals Cid <span dir="ltr"><<a href="mailto:aacid@kde.org" \
target="_blank">aacid@kde.org</a>></span>:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">El dimecres, 20 \
d'abril de 2016, a les 18:42:31 CEST, Elvis Angelaccio va<br> escriure:<br>
<span class="">> Hi,<br>
> as many of you already know, KDE has a github mirror in place at [1].<br>
> I've been playing with travis-ci [2] and I was surprised by how easy to \
use<br> > and how well integrated with github is.<br>
><br>
> I think it would be nice to have travis builds for the (mirrored)<br>
> repositories that provides a .travis.yml configuration file. The builds<br>
> would run on the travis servers, so no additional overload on the KDE<br>
> infrastructure. There is also virtually nothing to do for KDE sysadmins.<br>
> The project's maintainer is the one in charge to setup the travis<br>
> configuration file (if he wants to), in order to have working builds.<br>
><br>
> Would this be possible from a technical p.o.v.? I think the KDE github<br>
> account would have to register on the travis website and "sync" its \
github<br> > repositories - that's what I had to do with my personal github \
account.<br> ><br>
> The use cases could be many. For example, on travis I can install optional<br>
> dependencies that are not available on our Jenkins installation. More<br>
> details in this post [3].<br>
><br>
><br>
> What do you think?<br>
<br>
</span>I don't see the point in having two CI systems, just help improve the one \
we<br> have.<br>
<br>
If you need dependencies, why did you start a new CI system instead of asking<br>
for the dependendies to be installed?<br></blockquote><div><br></div><div>Well I did \
ask, but those deps are not available in the Ubuntu repositories currently used by \
Jenkins.<br></div><div>Maybe a solution could be to install them from \
source/manually, but that requires work from the sysadmins, who have already enough \
in their plate.<br><br></div><div>I did not start a new CI, I was basically playing \
with travis for fun. But then it turned out that it could solve an issue I have. The \
travis infrastrucure is already there, why not use it if one or more projects could \
benefit? Seems a win-win to me.<br></div><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Cheers,<br>
Albert<br></blockquote><div><br></div><div>Cheers,<br></div><div>Elvis<br> \
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"> <div class="HOEnZb"><div class="h5"><br>
><br>
> Regards,<br>
> Elvis<br>
><br>
><br>
> [1]: <a href="https://github.com/KDE" rel="noreferrer" \
target="_blank">https://github.com/KDE</a><br> > [2]: <a \
href="https://travis-ci.org/" rel="noreferrer" \
target="_blank">https://travis-ci.org/</a><br> > [3]:<br>
> <a href="http://www.aelog.org/travis-ci-builds-of-kde-projects-on-archlinux-chroot/" \
rel="noreferrer" target="_blank">http://www.aelog.org/travis-ci-builds-of-kde-projects-on-archlinux-chroot/</a><br>
<br>
<br>
</div></div></blockquote></div><br></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic