Update TravisCI config #1380
Update TravisCI config #1380
Conversation
Node 10 LTS support has ended, so we drop this from the "recommended" engines. TravisCI also updated to use the three even-numbered releases currently supported. Currently v12 is in Maintenance LTS, v14 is Active LTS and v16 is Current. npm 6.9 is the default version which shipped with NodeJS 12.
Our previous config would run `npm publish` for each node_js version (previously this was n=2, it's currently n=3). This resulted in errors as we were trying to publish the same (auspice) version number multiple times. This may or may not be related to the integrity shasum errors for auspice 2.29.0.
|
I would be surprised if there wasn't some stochastic issue involved if this has been happening all along where we try to publish to npm for multiple versions of node and it only just now caused the issue with 2.29.0. I also noticed this error with respect to updating the docker image: https://travis-ci.com/github/nextstrain/auspice/jobs/524607375#L576 that occured in one of the builds for 2.29.0 but can't say whether it contributed to this issue - it seems relatively unrelated. |
That would be my hunch too, but I wanted to take the chance to improve the Travis config here. Version 2.29.1 was successfully released using the config introduced in this PR. |
The npm Auspice 2.29.0 release had integrity shasum errors:
Looking through the TravisCI logs it became clear we were running
npm publishfor both versions of Node.js we ran TravisCI on, which resulted in one failure each time we released such asThis PR updates the Node.js versions we run CI on (v10 is no longer maintained), and only runs
npm publishwhen building under v14. It is not clear whether this is related to the integrity shasum errors, or if they were stochastic (or some other 🐛 ).