Skip to main content

Using Yeoman, Jenkins in Continuous Integration

Yeoman is a tool that will concatenate and minify your scripts, as well as, run JavaScript unit tests (JasmineBDD) inside a PhantomJS instance. It's fast and easy to integrate into your existing continuous integration process. At present, we have Jenkins as our work horse who will do the following upon each push to a specific development branch:
  1. Concatenate all JavaScripts based on a Gruntfile (GruntJS with NodeJS)
  2. Run JSHint on the concatenated JavaScript file (call this all.js)
  3. Minify the generated concatenated JS file (call this all.min.js)
  4. Run "yeoman test" to execute all the JavaScript specs against the concatenated JavaScript file
  5. 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!
1 comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.


Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:

Now, whenever you make a commit, it should show up like this in the log:

Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this

Want more emojis? check out the Emoji Mardown Cheatsheet!

World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…