I have recently set up several CI services in my cpython fork on Github: <https://github.com/abalkin/cpython/tree/ci>. I am not ready to make any recommendations, but feel free to click on the build badges at the top of the README file and see the results for yourself. I activated the following services: * Travis CI * CodeCov * CodeShip * AppVeyor (windows)
FWIW, you said they're "CI services": - CodeCov isn't actually a CI. - AFAIK CodeShip doesn't work on Windows, so, for Windows CI, there isn't really a choice *other* than AppVeyor. - CodeShip seems to require an account just to view the build status. - They're all failing. :( On Fri, Aug 5, 2016 at 10:19 AM, Alexander Belopolsky < alexander.belopolsky@gmail.com> wrote:
I have recently set up several CI services in my cpython fork on Github: <https://github.com/abalkin/cpython/tree/ci>.
I am not ready to make any recommendations, but feel free to click on the build badges at the top of the README file and see the results for yourself. I activated the following services:
* Travis CI * CodeCov * CodeShip * AppVeyor (windows) _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
-- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something’s wrong. http://kirbyfan64.github.io/
On Fri, Aug 5, 2016 at 4:39 PM, Ryan Gonzalez <rymg19@gmail.com> wrote:
FWIW, you said they're "CI services":
- CodeCov isn't actually a CI.
It is a "service." It is related to CI. It's not s stretch to call it a "CI service." It is a component that can be added to most CI providers.
- AFAIK CodeShip doesn't work on Windows, so, for Windows CI, there isn't really a choice other than AppVeyor.
I think you are right.
- CodeShip seems to require an account just to view the build status. - They're all failing. :(
Making the test run green is not a priority. Seeing failure reports is probably even more educational than seeing green badges. FWIW, I've added Circle CI to the mix and so far I like it the most.
On Fri, Aug 5, 2016 at 2:51 PM, Alexander Belopolsky <alexander.belopolsky@gmail.com> wrote:
FWIW, I've added Circle CI to the mix and so far I like it the most.
If you are in this exercise, I would also suggest trying with a hosted version of TeamCity. that seems extremely feature rich.
On Fri, Aug 5, 2016 at 6:21 PM, Senthil Kumaran <senthil@uthcode.com> wrote:
If you are in this exercise, I would also suggest trying with a hosted version of TeamCity.
I'd love to, but the only free provider I could find was <http://teamcity.codebetter.com/> and they seem to require a pre-approval. Do you know any other providers?
On Fri, Aug 5, 2016 at 3:48 PM, Alexander Belopolsky <alexander.belopolsky@gmail.com> wrote:
Do you know any other providers?
Unfortunately, No. Requesting codebetter.com for a trial seems ok. Otherwise, downloading the teamcity jar and running it locally is an option (just for trial). -- Senthil
Hmmm...maybe you'll find this interesting: https://strongloop.com/strongblog/node-js-travis-circle-codeship-compare/ -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something’s wrong. http://kirbyfan64.github.io/ On Aug 5, 2016 4:51 PM, "Alexander Belopolsky" < alexander.belopolsky@gmail.com> wrote:
On Fri, Aug 5, 2016 at 4:39 PM, Ryan Gonzalez <rymg19@gmail.com> wrote:
FWIW, you said they're "CI services":
- CodeCov isn't actually a CI.
It is a "service." It is related to CI. It's not s stretch to call it a "CI service." It is a component that can be added to most CI providers.
- AFAIK CodeShip doesn't work on Windows, so, for Windows CI, there isn't really a choice other than AppVeyor.
I think you are right.
- CodeShip seems to require an account just to view the build status. - They're all failing. :(
Making the test run green is not a priority. Seeing failure reports is probably even more educational than seeing green badges.
FWIW, I've added Circle CI to the mix and so far I like it the most.
On Aug 8, 2016, at 6:13 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
FWIW, I've added Circle CI to the mix and so far I like it the most.
Can you elaborate why you like it the most?
For me, the killer feature was ssh access to the build container. Circle CI simply adds your Github public key to the container instance and gives you an IP address to connect to. Overall, I agree with the authors of this blog post: <https://mediocre.com/forum/topics/a-tale-of-two-ci-tools-differentiating-travis-and-circleci>.
participants (4)
-
Alexander Belopolsky -
Antoine Pitrou -
Ryan Gonzalez -
Senthil Kumaran