search

trustdata / org

MIT Internet Trust Consortium
https://www.trust.mit.edu/
MIT License
0 stars 0 forks source link

CI/testing infrastructure #2

Open dmitrizagidulin opened 7 years ago

dmitrizagidulin commented 7 years ago

We need to decide on which Continuous Integration / automated testing service we'll be using on our repos. The simplest thing to start with is to use Travis CI on our public repos.

For the private ones, we can either pay Travis CI for seats, or set up a Jenkins server.

EternalDeiwos commented 7 years ago

I've already got a few repos (jwk + model) that are building with Travis CI, they're also set up for automated code coverage with codecov and istanbul. I am in favour of this approach, it's worked thus far for me.

Regarding private repos, it will probably be much easier to use Travis (the paid variety) if that's an option.

christiansmith commented 7 years ago

Really like the codecov integration with GitHub, it seems much better than what we have on the older repos. E.g., https://github.com/anvilresearch/jwk/pull/2

EternalDeiwos commented 7 years ago

Decision: Travis CI on Node 6.11.2, Codecov and Istanbul.

Linting to be added, but not included in CI until a later date.

christiansmith commented 7 years ago

@dmitrizagidulin which library were you proposing to use for standard js linting? feross? Got a link?

dmitrizagidulin commented 7 years ago

@christiansmith Proposing to use https://www.npmjs.com/package/standard. Which is just standard on the command line.