yipit/emerald

real-time continous integration server powered by node.js's crispy flakes

emerald's Issues

Notify the person who broke the build

Title: Notify the person who broke the build

Description

As an engineer
I want to get an email notification everytime I push changes that break the build
So that we that we can minimize the amount of time that other developers have to wait to check in

Background

Our CI server is constantly showing failed build on the TV, but since the developers are usually writting code jacked-in, would be optimal to have them notified as soon as they break the build

Acceptance criteria

Given there is a build instruction created in emerald
And that "Gabriel <[email protected]>" pushed a commit with failing tests
When the build finishes running
Then an email notification is sent to [e-mail]

Given there is a build instruction created in emerald
And that "Gabriel" which phone number is "[phone]" pushed a commit with failing tests
When the build finishes running
Then a SMS is sent to  "[phone]"

Given there is a build instruction created in emerald
And that I pushed a commit with failing tests
When the build finishes running
Then i see a growl notification poping on my screen

command line should take aditional options

The command line interface should accept a -c or --config option that stands for a path to a file that has a settings.js-compatible format, and will be merged with the default one.

So that the user will have the capability to overwrite some of the default options

Relative paths when using git clone

[EMERALD] [WEBSOCKET] INFO: transport end @18:43:22 GMT+0000 (UTC)
[EMERALD] [WEBSOCKET] INFO: handshake authorized @18:43:23 GMT+0000 (UTC)
[EMERALD] [WEBSOCKET] SUCCESS: enqueuing instruction #1 @18:43:24 GMT+0000 (UTC)
[EMERALD] [QUEUE CONSUMER] INFO: consuming the build queue: found an item to build @18:43:27 GMT+0000 (UTC)
[EMERALD] [ BUILD RUNNER ] INFO: preparing to fetch data from "Test" through "[email protected]:Yipit/yipit.git@dev" at /home/ubuntu/.emerald/builds/github-com-yipit-yipittest @18:43:27 GMT+0000 (UTC)
[EMERALD] [ BUILD RUNNER ] INFO: local copy does not exist, will clone at "/home/ubuntu/.emerald/builds/github-com-yipit-yipittest" @18:43:27 GMT+0000 (UTC)
[EMERALD] [ BUILD RUNNER ] INFO: spawning "git clone --progress [email protected]:Yipit/yipit.git github-com-yipit-yipittest" @18:43:27 GMT+0000 (UTC)
[EMERALD] [ BUILD RUNNER ] FAILURE: Error: ENOENT, no such file or directory '/home/ubuntu/.emerald/builds/github-com-yipit-yipittest/94157f39c276dda958d67a5aab2426c1.sh' @18:43:27 GMT+0000 (UTC)
[EMERALD] [ BUILD RUNNER ] FAILURE: Error: ENOENT, no such file or directory '/home/ubuntu/.emerald/builds/github-com-yipit-yipittest/94157f39c276dda958d67a5aab2426c1.sh' @18:43:27 GMT+0000 (UTC)

/usr/local/lib/node_modules/emerald/app/server/actors/buildrunner.js:302
build: build.toBackbone(),
^
TypeError: Cannot call method 'toBackbone' of undefined
at /usr/local/lib/node_modules/emerald/app/server/actors/buildrunner.js:302:26
at /usr/local/lib/node_modules/emerald/node_modules/async/lib/async.js:437:21
at /usr/local/lib/node_modules/emerald/app/server/actors/buildrunner.js:195:17
at Object.oncomplete (fs.js:608:21)

Nginx Proxying Broken with Github Post-Commit-Hooks

Attempting to put Nginx in front of Emerald to perform HTTP authentication.

I am able to get it to pass requests so that I can view the Emerald Page

http://ci2.yipit.com

But as soon as I try to hit a url that is not / I get the following errors:

https://gist.github.com/48c10bed8d1758c4d557

Gabriel suggested that it was an issue with Websockets and Nginx, so we switched to long polling, but it didn't seem to help.

Update the url of build links in the dashboard instruction box

The function that updates it is always using localhost instead of the parameter handled by settings.EMERALD_HOSTNAME.

Update the UI after building an instruction

After building an instruction, the dashboard is not being updated without a wild F5 click.

Failed builds are being shown green

Emerald should exactly show us which builds are broken, not hide it from us :)

timeout

builds should have a timeout, so that if the build takes longer than N seconds (to be defined in each build instruction), it aborts the build

Link to Github commits

It would be nice it builds from Github have a clickable link to jump to the commit hash on github so that you can review the code changes and/or make comments.

create HTTP hooks that activate builds

so taht we can hook github to it :)

Home Page refresh after failed build

After a build fails from the dashboard, the list of builds for a given project doesnt automatically update.

Insert and operations trying to remove null entries from redis

something wrong with the date...

110 years ago...

Instruction buttons on the dashboard should be more consistent

For example, when you start a new build and navigate to another page, like "Manage instructions", the button Abort will be hidden and the build one will appear again.

create a backbone view for editting/deleting a instruction

Git clone hangs on "https" urls waiting for a password

It's weird, but when a git clone runs with an https address, a password is required. If NO password is given and just an enter is pressed, things works like expected.

check if the output is being persisted properly

I think there is a bug

create a backbone view for listing and managing instructions

handle host key checking

when clonning a git repo, it should identify when it got stuck with host key checkign and preferably handle that

use ace wysiwyg editor for build scripts

@zmsmith had this neat idea:

use ace to edit build scripts, maybe we could even contribute with bash syntax highlight

Collect build stderr/stdout data and send to the live terminal

deleting an instruction should cleanup redis

#1. abort the current running build, if it's the case
#2. remove the associated builds from the queue

Create a new actor that pulls the repos from time to time

The BuildInstruction model should have a new field:

    it.has.field("poll_interval", kind.numeric);

That field will hold an interval in seconds that the repository should be polled for changes.

When set to 0 it means the instruction will never poll the repository for changes

handle redis problems

and log to the screen properly

create a git-poller actor

There should be an actor for polling git from times to times and run the builds when necessary

It should be easy to run emerald in debug mode

Currently, to debug emerald and use the amazing node-inspector, I have to patch the first line of the file /app/terminal/main.js. A better solution would not touch this line, but automate it via npm actions.

only create ticket for breaking tests if all previous commits succeeded for that particular test

when a build breaks and it's previous build was succeeded, then a HTTP hook should be called

Growl Style Dropdown's have localhost for image path.

http://imgur.com/5MgNC

I can show you as well, hard to copy since the JS goes away fairly quickly.

create a backbone view for creating instructions

Show the stderr/stdout of a build when using the respective buttons in the dashboard

Not sure, but at least for a while, it would be enough to send the user to the #build/ view.

create a command line

to start the server

emerald start

serving on http://localhost:8000

emerald :8000 # localhost:8000

serving on http://yourdomain.com

emerald yourdomain.com:80

manage instructions

emerald instruction create 

will drive you to an interactive REPL

Let's create a new instruction for emerald

type help anytime to show this

filing commands: will fill up the project name and show the missing fields

    name, description, script, repository, branch

emerald>

create a backbone view that is a full-screen terminal

it should have auto-scroll to bottom as more data is streamed

preferably will also parse ANSI colors

rewrite the build runner to be a fork

The run of a build should happen in a separated module (actor) that will be ran through

var be = child_process.fork('build_executer')
current_build.pid = be.pid;
current_build.save(function(){
  be.send({current_build: current_build, instruction: self});
});

so that when a build is aborted will only be necessary to kill a pid

replace jquery.gritter with humane.js

The "jackedup" theme of humane.js will suit perfect to emerald: http://wavded.github.com/humane-js/