search

docopt / docopts

Shell interpreter for docopt, the command-line interface description language.
Other
501 stars 53 forks source link

travis.org seems gone, we need to find something else? #54

Closed Sylvain303 closed 2 years ago

Sylvain303 commented 3 years ago

There was a CI builder, which mainly useful for macos building.

It seems it's no more working:

https://travis-ci.community/t/org-com-migration-unexpectedly-comes-with-a-plan-change-for-oss-what-exactly-is-the-new-deal/10567

Do we need a CI for docopts? How to setup a new CI?

agilgur5 commented 2 years ago

Travis CI moved to travis-ci.com and not the same OSS experience anymore

So I had to manually re-set-up Travis on travis-ci.com (instead of .org) recently in one of my projects react-signature-canvas (c.f. https://github.com/agilgur5/react-signature-canvas/pull/69 , https://github.com/agilgur5/react-signature-canvas/pull/64#issuecomment-1030886888) after learning of all these relatively recent changes.

Basically you can migrate to travis-ci.com and then you have to email support to ask for OSS credits once you use up your free credits. It's not a great system, and per the forum link you shared, sometimes it can be non-trivial to get those credits too... It's also a really manual, tedious process to migrate to .com, especially as you have to change all your webhooks etc as well.

I could help guide you through that, if you'd like, but it's not my account, so can't do it for you.

Alternatives -- GitHub Actions

The Alternative is to switch to a new CI provider. Most folks have moved to GitHub Actions since that is free for OSS as well and Actions are are more shareable than many other CI provider options (e.g. CircleCI Orbs, etc (sidebar: though Dagger, founded by Docker co-founder Solomon Hykes, promises to eventually have a cross-platform composable CI toolkit that can run on any CI provider)).

I can help by starting to write up a PR for a GitHub Actions workflow that would mimic the Travis workflow

Sylvain303 commented 2 years ago

So, « Do we need a CI for docopts? » Answer is yes for testing and ensuring macos specific code still works.

So I suppose we could go to github Action:

https://github.blog/2022-02-02-build-ci-cd-pipeline-github-actions-four-steps/

So avoiding cross-site sharing breaking api too often. :crossed_fingers:

The .travis-ci.yml was quite strait forward with some hack to ssh back to macos VM if something went wrong. :wink:

See reverse_ssh_tunnel.sh for gory details if you're curious. But ignore it for now.

Of course the license stuff... :disappointed: I hope it wont put so much stick in our wheel.

I still have to read more about github Actions.

agilgur5 commented 2 years ago

See reverse_ssh_tunnel.sh for gory details if you're curious. But ignore it for now.

I read it before, I was like "oh this is how you debugged on Mac", was not expecting that 😅

So I suppose we could go to github Action

If you're ok with that route, I can get to work on a PR for that

Sylvain303 commented 2 years ago 
So I suppose we could go to github Action

If you're ok with that route, I can get to work on a PR for that

Yes go for it, I suppose I was waiting for another mac user knocking at my door. :wink:

agilgur5 commented 2 years ago

@Sylvain303 sorry for the long delay on this, but I just opened a PR #62 to migrate to GH Actions!

(I ended up becoming a maintainer of rollup-plugin-typescript2 around the same time as my comments here, so that ended up taking up my OSS time for quite a while as a result 😅 But finally got back to this!)

Sylvain303 commented 2 years ago

Hello, @agilgur5 Great that you did spent some time on it. I'm really quite busy myself not working on the docopts project actually. So I'm now reviewing the changes you made.

Thanks for the contribution. :smile: