aboutsummaryrefslogtreecommitdiffstats
path: root/Gruntfile.js
Commit message (Collapse)AuthorAgeFilesLines
...
* build: Use blacklist instead of whitelist for jshint/jscs/jsonlintKunal Mehta2015-07-231-26/+7
| | | | | | | | | | | | | | | | | | | | * jsonlint now includes docs/, includes/ (api and installer i18n), maintenance/, and tests/. 539 files -> 864 files. - Continue to exclude JSDuck artefacts in docs/js/. - Continue to exclude vendor/. * jshint now includes mw-config/ and maintenance/. 177 files -> 179 files. * jscs now includes everything jshint includes. 172 files -> 179 files. - The -skip.js files no longer need excluding. Use the native exclude syntax for jshint and jscs so that other software and services with JSHint support use these as well. Change-Id: Idebf30275f9c93483069367f923ed290c38e0b26
* Gruntfile.js: Remove unused 'pkg'Kunal Mehta2015-07-101-1/+0
| | | | | | It's unused and ends up being copied into a bunch of repositories that also don't need it. Change-Id: Icf81b3ae13e510670bde38c1c8d7ef42917b7c2a
* build: Increase qunit browserNoActivityTimeout from 10s to 60sTimo Tijhof2015-03-201-1/+3
| | | | | Bug: T89075 Change-Id: I3ef601a38052e38247cebfb19475a31ac2448eac
* build: Add assert-mw-env task when running grunt-qunitTimo Tijhof2015-03-201-1/+14
| | | | | | | | | Previously it gave cryptic error messages like: > Running "karma" task > > Warning: Parameter 'url' must be a string, not number Change-Id: I0adb0f2f501dd5db2d6738a40efbce349f0175d2
* Rename JSDuck config to standard 'jsduck'Timo Tijhof2015-03-091-0/+11
| | | | | | | | | | | | | | | | | | | | * Move configuration to /jsduck.json per standard. This way it can be run as plain '$ jsduck' without needing a maintenance script or custom Jenkins job. Similar to JSHint, JSCS, Grunt, and Gem etc. * Move --processes=0 from maintenace script into config file. This should've been in the config file all along and serves as workaround for https://github.com/senchalabs/jsduck/issues/525. * Use grunt-contrib-copy instead of a symlink for resources. For local development a symlink works fine, but for publishing from Jenkins to doc.wikimedia.org the /docs/js/ directory needs to be standalone. This was previously done with a manual post-build step that added an additional rsync, but this logic should be in the repository so that the doc entry point can be simplified and standardised to 'npm run-script doc' for all projects. Change-Id: Iaaaac50ee78dd9ff8f24f1ef3a3685ad51cf33b2
* test: Don't run the npm pipeline for the now-empty skins directoryJames D. Forrester2015-02-141-1/+1
| | | | Change-Id: I426835c83c0dd73fa7247ed2ec299cdec1e43fcb
* Gruntfile: Clean up Karma configTimo Tijhof2015-01-311-22/+5
| | | | Change-Id: I8197c2b0169983c32a44397faec95ad7eb47ab86
* tests: Move npm-test to repo rootTimo Tijhof2015-01-141-0/+111
This is way overdue as it isn't experimental anymore. Keeping it in a non-standard subdirectory makes it harder to discover for people. And makes it harder to run from Jenkins since this is already being ran on every commit. Related to 70f3919. Change-Id: Iaf5cf65616f82640145fbb6395c36129428602ca