ejholmes

{
    "length" : 0,
    "name" : "DateTime__c",
    "type" : "datetime",
    "defaultValue" : null,
    "label" : "DateTime",
    "updateable" : true,
    "calculated" : false,
    "caseSensitive" : false,
    "controllerName" : null,

ejholmes

• Databasedotcom
• Janky
• Catapult
• JWPlayer
• wysihtml5

ejholmes

CI Build Status for Github

TL;DR Add an api that allows external CI systems to tag commits with a build status

I suggest that Github add an API to allow third party continuous integration systems, such as Travis or Janky, to be able to tag commits with a build status. This information could then be brought in with each commit under pull requests to quickly see the health status of a branch.

API

POST /repos/:user/:repo/commits/:sha/build_status

ejholmes

task :watch do
  system "coffee -cw janky.coffee"
end

ejholmes

# Heroku sitemap

primary:
-
  Platform: http://heroku.com
  How It Works: http://heroku.com/how
  Pricing: http://heroku.com/pricing
-
  Add-ons: http://addons.heroku.com
  Catalog: http://addons.heroku.com

ejholmes

Eric Holmes

GitHub | LinkedIn | Blog

I'm a passionate full stack developer with extensive experience with both server side and client side MVC frameworks. My development stack of choice includes Git, Ruby on Rails, SASS, CoffeeScript, CSS3 and HTML5. I'm a firm believer in test driven development, continous integration and code review, and always strive to write beautiful and elegant code that solves complex problems easily.

ejholmes

$(function() {
    Player.setup({
        jwplayer: 'demoplayer/jwplayer',
        playlist: 'demoplayer/xml/nav-gwy.xml',
        playlistfile: 'demoplayer/xml/nav-gwy.xml',
        jwplayer_options: {
            autostart: false
        }
    });
});

ejholmes

$(function() {
    Player.setup({
        playlist: [
            {
                duration: 10,
                image: 'examples/images/preview1.png',
                title: 'Imperdiet',
                levels: [
                    { file: 'examples/video/video1.mp4' },
                    { file: 'examples/video/video1.webm' }

ejholmes

window.gmaps_style = [
    {
        featureType: 'all',
        elementType: 'all',
        stylers: [
            { hue: '#000000' },
            { saturation: 0 },
            { lightness: 0 },
            { visibility: 'on' }
        ]

ejholmes

The following is how I'm currently advising folks to use Jasmine with Rails 3.1:

Here's how to set up jasmine with the asset pipeline on a Rails 3.1 project:

1. Point at HEAD of jasmine ("gem 'jasmine', :git => "git://github.com/pivotal/jasmine-gem.git")

2. Add the following line to spec/javascripts/support/jasmine_runner.rb (after require 'rubygems' is good, I think): require File.expand_path("../../../../config/environment", FILE)
3. Change your application.js manifest to include the jquery files you want
4. Include /assets/application.js and nothing else in your src_files.
5. Run jasmine, it should pick up jquery, etc. You should also be able to load anything you need from your asset pipeline via /assets/, as long as you use a full path (ie, we can't glob up files from your asset pipeline).