Connect a CI Checks API tool

[jhuntwork]

If you look here you can see that Github has an API that third-party tools can hook into for running code tests on new PRs, and possibly other pipeline shapes. This lets us dynamically run tests each time someone wants to merge something.

Of the ones that are offered, it looks like these three are free for open source:

• Travis CI
• Cirrus CI
• Azure Pipelines

I've used Travis before, it's not bad. I'm not sure how the other two compare. Cirrus seems pretty much the same as Travis. Azure looks like it might offer more. It is Microsoft ;) but they seem to be more eager to play nice these days.

[SheepReaper]

Appveyor I believe is also free for open source.

…

On Fri, Apr 26, 2019, 1:18 PM Jeremy Huntwork ***@***.***> wrote: If you look here <https://github.com/automate-lfs/jhalfs/pull/1/checks> you can see that Github has an API that third-party tools can hook into for running code tests on new PRs, and possibly other pipeline shapes. This lets us dynamically run tests each time someone wants to merge something. Of the ones that are offered, it looks like these three are free for open source: - Travis CI - Cirrus CI - Azure Pipelines I've used Travis before, it's not bad. I'm not sure how the other two compare. Cirrus seems pretty much the same as Travis. Azure looks like it might offer more. It is Microsoft ;) but they seem to be more eager to play nice these days. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLQ6JLQ42XYPE7Q3WVV7UTPSM2MNANCNFSM4HIX4Z6Q> .

[pierre-labastie]

I'm all for this, but I think I shouldn't try to do too much, otherwise, I'll just sink... So: your choice (I'd suggest Travis, if you have experience with it, hoping that it can be changed later, need it to be). Just let me know if I should do something on my part ("buy" the application for the organization for example).

[jhuntwork]

No problem, I'm happy to set up the CI parts and provide some guidance around it. I do this kind of thing a lot for work. Yes, Travis should be fine to start and we can always swap it out for something else down the line. If you can 'buy' the free version for the public open source repo, that'd be great, thanks.

[pierre-labastie]

I think I've authorized Travi CI to access our organization repositories. Whether this is enough for @jhuntwork to do something or if there is more needed, I cannot tell... It it is enough, can you close this issue?

[jhuntwork]

Great, thanks! I will take a look today and maybe even connect up a quick test.

[pierre-labastie]

Reviewing issues. Maybe this one could be closed.
@jhuntwork Have you succeeded in adding those CI tests (I know master is broken right now, so maybe revert it to what it was before my unfortunate changes, in order to test the test :)

[pierre-labastie]

@jhuntwork Maybe you needed me to merge your PR #19, sorry for taking so long...

[jhuntwork]

No worries, I haven’t been able to give it much attention lately either.

…

On Mon, Sep 16, 2019 at 08:07 Pierre Labastie ***@***.***> wrote: @jhuntwork <https://github.com/jhuntwork> Maybe you needed me to merge your PR #19 <#19>, sorry for taking so long... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AAB2QCQL4ZPPGB34GGR3IUDQJ5ZGXA5CNFSM4HIX4Z62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Y5RIA#issuecomment-531749024>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB2QCXBHL5N53YMUZF44S3QJ5ZGXANCNFSM4HIX4Z6Q> .