- Concatenate all JavaScripts based on a Gruntfile (GruntJS with NodeJS)
- Run JSHint on the concatenated JavaScript file (call this all.js)
- Minify the generated concatenated JS file (call this all.min.js)
- Run "yeoman test" to execute all the JavaScript specs against the concatenated JavaScript file
- This should fail the build process if any specs fail or if JSHint chokes
At this point, you could ship the assets over to CDN on Amazon CloudFront or Windows Azure Blob (CDN) to further reduce latency for your users.
Below is a shell script that can be easily modified to fit your needs:
yeoman concat min --disable-insight --no-color
rm -rf src/test/build
cp -R src/main/MYAPP/public/javascripts src/test/build
yeoman test --disable-insight --no-color
Above, you'll see that we're removing the src/test/build directory, which is just a directory that contains all your JavaScript assets. In the next line, we copy over the application's JavaScript files to the src/test/build folder. One thing to note is that the src/test folder is actually where the Jasmine BDD Test Runner resides.
In trying to integrate Yeoman into your pipeline, you'll most likely hit this feature where it prompts the user to allow 'analytics for usage'. You can disable this prompt by adding the "--disable-insight" flag. The reason why you'd want to disable this feature is because it will cause builds to fail on Jenkins if it comes up.
Happy front-end development!