You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@annotator.apache.org by GitBox <gi...@apache.org> on 2018/06/19 20:02:32 UTC

[GitHub] BigBlueHat opened a new issue #36: Continuous Integration

BigBlueHat opened a new issue #36: Continuous Integration
URL: https://github.com/apache/incubator-annotator/issues/36
 
 
   I've started a basic [travis-ci.org](https://travis-ci.org/) setup via [a personal fork](https://travis-ci.org/BigBlueHat/incubator-annotator).
   
   This has raised a few questions:
    - do we want to use travis-ci?
      - I've no preference; Infra's set it up for others before...but also may not care in practice
    - @tilgovi mentioned that the top-level package needs node 8+ whereas the `packages/` need node 6+
      - however...I've not been able to sort configuring travis in such away as to accommodate that...
   
   Here's what I've got so far:
    - GitHub branch: https://github.com/BigBlueHat/incubator-annotator/tree/travis-ci
    - Latest Travis run: https://travis-ci.org/BigBlueHat/incubator-annotator
   
   My last attempt includes using `node` as the `node_js` version via `.travis.yml` and attempting to use `.nvmrc` files for local `packages/` folders. Turns out Travis doesn't check all those...
   
   There's also the question of narrowing the test runs to just each individual package.
   
   Anyhow. It's doable, but there's a lot more to do...

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services