-
Notifications
You must be signed in to change notification settings - Fork 197
Open
Description
Hi,
We are getting flakey errors when fetching jasmine-core from npmregistry in jenkins. In grunt-contrib-jasmine/tasks/lib/jasmine.js jasmineCoreFolder = path.join('node_modules', 'grunt-contrib-jasmine', '.jasmine', options.version); it seems to try to find jasmineCoreFolder in .jasmine and if it doesn't exist, it tries to fetch jasmine-core from registry. On each clean build, .jasmine is missing so it always fetches package first. Is it possible to specify jasmine-core directory as part of options to avoid fetching jasmine-core on first run?
We are using grunt-contrib-jasmine=4.0.0
Thank you!
Metadata
Metadata
Assignees
Labels
No labels