-
Notifications
You must be signed in to change notification settings - Fork 149
Make CI slow by validating against master definitely typed #718
base: master
Are you sure you want to change the base?
Conversation
- git clone https://github.com/DefinitelyTyped/DefinitelyTyped ../DefinitelyTyped | ||
|
||
script: | ||
- npm tes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- npm tes | |
- npm test |
- npm run build | ||
- npm run clean | ||
- npm run parse | ||
- npm run check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- This isn't very valuable, it mostly just tells you what
@types
packages are superceded by in-package types. - On the other hand, we shouldn't never run it.
- On the third hand, it'll make CI slow.
- Is CI never not slow?
- This is probably the right place to run it.
- npm run build | ||
- npm run clean | ||
- npm run parse | ||
- npm run check | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably should npm run calculate-versions
and npm run generate
and npm run index
.
Note that some of these tasks hit npm (parse, index and maybe generate?)
- npm tes | ||
- npm run build | ||
- npm run clean | ||
- npm run parse |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This relies on a cache to avoid querying npm for everything. It is NOT the most reliable cache, and I don't understand travis' caching strategy. You should test to see whether it's running npm info
on every @types
package for every CI run. If it's not, then you need to make sure that it's correctly running npm info
on packages that were recently updated in DT.
This clones DT into a sibling folder, then runs through everything up till deployment on CI