For the context, I wrote that little "wrapper" to communicate with their v3 API.
Back then, after I got a new computer I tried to install their CLI but didn't succeed. So I looked for a real alternative wrote in Python as the management tool I was planning was written in Python (private source).
I tried travispy which was quite interesting to use but it failed to convince me as I was looking to use some of the unique features of the API v3 of Travis CI.
Therefore, I created PyTravisCI which exclusively supports their API v3. It got a complete rewrite last year to be more performant while trying to be "developer-friendly". As of today, it implements 90-95% of its endpoints and features.
I'm not sure if it is used by someone else, but if we choose to trust pepy.tech [1], it had over 38 000 total downloads since it exists. And those downloads are not from me as I manually upgrade my node (once) only after a new release of PyTravisCI into the PyPI. And that does not happen so often.
My goal was to write something for myself but in the hope to also help others. So any feedback or contribution is welcome!
I'm the author of that piece @detaro.
For the context, I wrote that little "wrapper" to communicate with their v3 API. Back then, after I got a new computer I tried to install their CLI but didn't succeed. So I looked for a real alternative wrote in Python as the management tool I was planning was written in Python (private source).
I tried travispy which was quite interesting to use but it failed to convince me as I was looking to use some of the unique features of the API v3 of Travis CI. Therefore, I created PyTravisCI which exclusively supports their API v3. It got a complete rewrite last year to be more performant while trying to be "developer-friendly". As of today, it implements 90-95% of its endpoints and features.
I'm not sure if it is used by someone else, but if we choose to trust pepy.tech [1], it had over 38 000 total downloads since it exists. And those downloads are not from me as I manually upgrade my node (once) only after a new release of PyTravisCI into the PyPI. And that does not happen so often.
My goal was to write something for myself but in the hope to also help others. So any feedback or contribution is welcome!
[1]: https://pepy.tech/project/pytravisci