On Tue, Feb 26, 2019 at 1:49 PM JJ Merelo <[email protected]> wrote:
> Hi, > > El mar., 26 feb. 2019 a las 11:34, Fernando Santagata (< > [email protected]>) escribió: > >> Hello, >> >> Today I stumbled upon this article: >> >> https://blog.steve.fi/experimenting_with_github_actions.html >> >> the first line of which is: >> >> Recently I heared that travis-CI <https://travis-ci.org/> had been bought >>> out <https://news.ycombinator.com/item?id=18978251>, and later that >>> they'd started to fire their staff >>> <https://news.ycombinator.com/item?id=19218036>. >>> >> >> I'm not a big fan of Travis-CI's. In the past I found out that the Ubuntu >> Xenial perl6 container wrongly redirect to the Precise one; I raised the >> issue on their community forum, since the perl 6 language is >> community-maintained, but I received no feedback so far. [¹] >> > > I use Travis all the time, and it's used by default in the Perl 6 > ecosystem. I don't like the default perl6 travis configuration, which > compiles Perl 6 via rakudobrew every single time. I generally use either a > generic docker container, test-perl6, or custom containers such as the one > created for the ecosystem or the documentation. > >> >> Any thoughts on this topic? Is anyone going to prepare a perl6 recipe to >> use with Github actions? Any other alternative to Travis-CI? >> > > Can you use GitHub actions for CI? If that's the case, we should probably > do that. Are they hosted by GitHub? > Apparently those "actions" are available directly from Github, as reported by the article I quoted. Today I noticed that in the last issue of p6weekly ( https://p6weekly.wordpress.com/2019/02/25/2019-08-inline-scalaring/) Liz writes: Nick Logan added support for CircleCI. > So, yet another possible choice. When $dayjob leaves me some spare time I will give a try to both Github actions and CircleCI. > We also use shippable with the Perl 6 documentation, and Appveyor is also > used here and there. Recently, apparently Circle-CI has been set up to test > Rakudo, so it might be another option. > >> >> >> [¹] I cooked up a solution to that problem. If anyone is interested see >> for example: >> >> https://github.com/frithnanth/Perl6-Desktop-Notify-Progress/blob/master/.travis.yml >> which runs in 1' 11" ( >> https://travis-ci.org/frithnanth/Perl6-Desktop-Notify-Progress), but >> needs continuous updates, since there's no "latest" link in the Perl 6 >> packages page (https://github.com/nxadm/rakudo-pkg/releases) which the >> script uses to install Perl 6 in the container. >> > > > Using either those packages or available docker containers is always > better option than the default travis configuration, from my POV > > Cheers > -- > JJ > -- Fernando Santagata
