BLD: move asv build to a daily travis cron

[jreback]

[TomAugspurger]

Are you working on this, or should I?

[jreback]

feel free!

I would create another repo (in pandas-dev) to do this
similar to the wheel building

i suppose u could reuse that code

[TomAugspurger]

Good idea. Thoughts on moving over

1. ASV
2. conda-build
3. pip build

Anything else?

[jreback]

i think those plus 32 bit build would be awesome

maybe just run these on a daily cron

[jreback]

maybe doc build as well?

[TomAugspurger]

I think Joris had plans (or hopes?) to move the doc build to circle-CI and upload an artifact so that users can check the doc build, similar to how scikit-learn does it.

…

On Wed, Feb 14, 2018 at 5:58 AM, Jeff Reback ***@***.***> wrote: maybe doc build as well? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19695 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQHIu0Qltd9xWgFpXNqvMlj4zCytxfxks5tUsplgaJpZM4SFIXG> .

[jreback]

even better!

note that we do this also in ibis-project

[TomAugspurger]

👍 . I'll be offline for a couple hours, but will start on this afterwards.

Tangentially related, I'd like to go through all our ci/* stuff and simplify / consolidate our dependency code.

I want to get to the point where we have a single environment.yaml per build, and try to get everything installed in a single shot by conda, instead of multiple steps. That'll help with previously pinned deps getting upgraded without us knowing.

And then we can small script that will print out the various versions of deps we're tested against.

I'd also like to better manage optional dependencies and test-only dependencies, but not sure the best way forward yet.

[jreback]

all for cleaning up
but be careful
a lot of that code is designed to give informative errors when things fail and to no pin things too much

[jorisvandenbossche]

I think Joris had plans (or hopes?) to move the doc build to circle-CI and upload an artifact so that users can check the doc build, similar to how scikit-learn does it.

Even apart from that, I often check the doc build to then comment on the PR with things that break the docs, so I would prefer to keep this in the pandas CI itself.

[TomAugspurger]

FYI: https://travis-ci.org/pandas-dev/pandas-ci/ if you want to sign up for alerts on build failures, though maybe wait until I get a successful build first :) Then I'll switch it over to a daily cron. I'm doing conda build and ASV now. Pip build with no Cython will follow once we figure out why it's broken.

…

On Wed, Feb 14, 2018 at 10:07 AM, Joris Van den Bossche < ***@***.***> wrote: I think Joris had plans (or hopes?) to move the doc build to circle-CI and upload an artifact so that users can check the doc build, similar to how scikit-learn does it. Even apart from that, I often check the doc build to then comment on the PR with things that break the docs, so I would prefer to keep this in the pandas CI itself. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19695 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQHIkJhPMV14TdtJxr1T6y_vhqMaKUjks5tUwSrgaJpZM4SFIXG> .

[jreback]

yeah not concerned about the doc build really. the other builds are just taking extra time on each commit and doing daily would be sufficient.