choderalab / software-development

A primer on software development best practices for computational chemistry
262 stars 78 forks source link

Continuous integration #3

Closed jchodera closed 7 years ago

jchodera commented 7 years ago

We should cover continuous integration for testing of software and packaging.

We currently use

We also use https://nightli.es/ for triggering nightly builds to make sure code doesn't go stale due to changes in upstream dependencies.

We try to make this easier by using a devtools/ boilerplate: https://github.com/omnia-md/devtools

Lnaden commented 7 years ago

@jchodera We'll need the docs you already have on configuring travis and appveyor

Are there other CI platforms we recommend?

jchodera commented 7 years ago

@marscher has been exploring CircleCI as an alternative to travis, with some interesting features.

Lnaden commented 7 years ago

Interesting, I'll see if there is anything in there to bring into the writeup

jchodera commented 7 years ago

I think the support for retrieving build artifacts could be useful.