Sparrow(do)!

Sparrow6/Sparrowdo – Raku Automation

RakuDist Update. Long Queue Short.

Hello!

RakuDist is a service that enables Raku module authors to test theirs distribution across different Rakudo and OS versions.

A lot of things have happened to the project recently.

I am to busy to write all the details, but to make a long story short, there are two important facts.

RakuDist has got a nice web UI, so people could launch builds by using convenient html form, try it now!

http://repo.westus.cloudapp.azure.com/rakudist2

In the future I’ll probably find a proper domain name for the service, but so far it’s the link just mentioned.

And secondly, RakuDist is now powered by Sparky backend, which means all the builds are 100% asynchronous queues and hopefully my VM will cope with a load if people start using the service proactively.

That is it. Thank you for reading. I’d appreciate comments as usual from Raku community.

Best.

Alexey

 

 

melezhik

3 responses to “RakuDist Update. Long Queue Short.”

  1. cxw Avatar
    cxw

    I’ve been wondering: is RakuDist eventually going to evolve into Raku’s CPANTesters? Is there any fully-automated smoke testing for Raku modules yet? Thanks!

    Like

    Reply
  2. melezhik Avatar
    melezhik

    Hi @cxv! I don’t know to be honest. So far RaluDist is a convenient way to test Raku distribution with just one click deployment. When _authors_ triggers
    builds for their modules. You can also trigger travis builds and launch RakuDist from external systems using HTTP API .

    CPANTesters on my view is more about reporting zef install errors from users machines back to centralized server, rather then authors run tests intentionally … ( I may be wrong on this part here, CPANTester has also a dedicated team that pick modules randomly an test them, but the RakuDist is first of all is targeted to Raku modules authors )

    So logically those two systems have different purposes, though aiming to solve pretty much the same task – insuring modules / rakudo versions are not broken. But as you can see in different ways.

    As for the “Is there any fully-automated smoke testing for Raku modules”, I am not aware of any existing tools, but RakuDist allows people fully automate the process of testing their modules, because it’s only `zef install` but much more. For example this:

    – https://sparrowdo.wordpress.com/2020/02/22/testing-command-line-applications-using-tomty-and-rakudist/

    And that

    – https://sparrowdo.wordpress.com/2020/02/11/rakudist-update-travis-integration-and-post-deployment-tests/

    And that

    – https://sparrowdo.wordpress.com/2020/01/28/rakudist-update-raku-modules-installation-customization/

    If you be more specific about your requirements, I’d happy to give your more details and guidelines how to use RakuDist/Sparrow in that way …

    HTH

    Alexey

    Like

    Reply
  3. 2020.19 Release Release – Rakudo Weekly News

    […] Melezhik updates the community on RakuDist changes (/r/rakulang […]

    Like

    Reply

Leave a comment