customink/stoplight

Hook it up to your builds and see their status from anywhere in the room

stoplight's Issues

Periodic ERROR message in logs

E, [2013-07-18T16:55:23.932865 #16502] ERROR -- : execution expired: http://travis-ci.org/repositories.json

Looks like it might come from here:
https://github.com/customink/stoplight/blob/master/lib/stoplight/providers/travis.rb#L14-L16

URL doesn't exist, afaik.

Once using https://api.travis-ci.org/ as the server, clicking a project icon breaks

Ref #19

Changing the server value to https://api... breaks other functionality, like clicking on a failing project used to direct the user to the Travis page.

stoplight redesign-white

Hi guys,
Sorry for the late response, been quite sick this week. We had a little discussion over twitter, if you remember, so I cleaned up what I was working on and able to present this demo:

http://stoplight-white-demo.herokuapp.com/index.html

Take into account its very packed (jruby CI) so that it will showcase all of the range of UI concepts it holds.

This is a major step away from the existing stoplight UI. Here is the logic / reasoning behind it:

These are the goals I've set to myself;

Stoplight is an information radiator. The key goals are to radiate health, and current activity of all projects.

More detailed, Stoplight needs to display the current status of every project, it should indicate a building project distinctively, it should also give a sense of time across the board, each project should be eyed with a glance easily (with no need to seek it), it should display all projects to provide a solid grasp for the overall health with a glance.

Practically, this meant:

• current status is displayed by color keys (gray, red, green) with the build circle, and on cases (see below) on the title itself
• a building project is displayed by a fade-in-fade-out circle
• the sense of time, is pronounced as follows: for a freshly successfully built project - its title will remain lit green for an order of minutes or hours (configurable). A successful non-fresh project is gray with a green circle. A very old ("old" is configurable) successful non-fresh project is losing its grayness gradually becoming very light gray. A failed project will always remain red regardless of time.
• no need to seek for projects every time again. this is because projects are sorted alphabetically and remain consistent on the board regardless of build time (which is the most natural order for humans to seek on). This means we can no longer sort by build date (this is why I chose fading colors to represent the sense of time)
• all projects are displayed at once.

This, if you choose to accept is, what I'm offering on my fork :)

I didn't bother with a pull request because I understand that this is a significant departure from the current UI, so let me know if this make sense for you

Have a good one.

ERROR NoMethodError: undefined method `write'

Hi,

I got following stacktrace when trying to run the server:

[2012-09-25 08:34:26] INFO  WEBrick 1.3.1
[2012-09-25 08:34:26] INFO  ruby 1.8.7 (2010-01-10) [i486-linux]
[2012-09-25 08:34:31] INFO  WEBrick::HTTPServer#start: pid=23823 port=9292
10.0.0.51 - - [25/Sep/2012 08:34:51] "GET / HTTP/1.1" 404 435 0.0177
[2012-09-25 08:34:51] ERROR NoMethodError: undefined method `write' for #<Logger:0xb6f085f0>
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/commonlogger.rb:33:in `log'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/commonlogger.rb:22
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/body_proxy.rb:17:in `call'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/body_proxy.rb:17:in `close'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/lint.rb:555:in `close'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/body_proxy.rb:15:in `close'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/handler/webrick.rb:75:in `service'
        /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
        /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
        /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
        /usr/lib/ruby/1.8/webrick/server.rb:162:in `start'
        /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
        /usr/lib/ruby/1.8/webrick/server.rb:95:in `start'
        /usr/lib/ruby/1.8/webrick/server.rb:92:in `each'
        /usr/lib/ruby/1.8/webrick/server.rb:92:in `start'
        /usr/lib/ruby/1.8/webrick/server.rb:23:in `start'
        /usr/lib/ruby/1.8/webrick/server.rb:82:in `start'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/handler/webrick.rb:13:in `run'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/server.rb:265:in `start'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/lib/rack/server.rb:137:in `start'
        /usr/lib/ruby/gems/1.8/gems/rack-1.4.1/bin/rackup:4
        /usr/bin/rackup:23:in `load'
        /usr/bin/rackup:23

Any ideas what it could be?

Ruby = 1.9.1

RubyGems = 1.8.24

cheers

undefined method `iso8601`

I used the stoplight recipe to install stoplight. The installation process went fine. But when I hit the server, it returned 500 internal error.

A quick look at the httpd/log/error.log showed the following:

[WARNING] MultiJson is using the default adapter (ok_json). We recommend loading a different JSON library to improve performance.
NoMethodError - undefined method `iso8601' for #<DateTime: 53051722853/21600,0,2299161>:
        ./views/index.erb:27:in `evaluate_source'
        ./views/index.erb:22:in `each'
        ./views/index.erb:22:in `evaluate_source'
        /usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/template.rb:144:in `cached_evaluate'
        /usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/template.rb:127:in `evaluate'
        /usr/lib/ruby/gems/1.8/gems/tilt-1.3.3/lib/tilt/template.rb:76:in `render'
        /usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:636:in `render'
        /usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:522:in `erb'
        ./application.rb:27:in `GET /'

I am running a centOs 5.6 x86_64, chef-0.10.8, ruby 1.8.7 (2011-06-30 patchlevel 352) and gem 1.8.10.

Thanks,

Nothing showing

After I've configured a server in the config file and I visit the page I get the "Sinatra doesn’t know this ditty" page showing up.

If I visit /projects.json I do get a list of jobs from Jenkins. I don't know if I'm doing something wrong or if it might be related to stoplight.