Provide a button on the UI to purge all the builds

In order to confirm it is capable of running its own suite, we need a UI

Use this instead of the forking we are doing right now
https://github.com/brandonhilkert/sucker_punch

When the build passes, execute .bait/pass.sh if it exists.

Set it to 8417

In order to prepare the objective c source files for a clean static compilation, we should add a new feature to Bait::ObjectiveC::Project

So instead of this:

  path = File.expand_path('../..')
  project = Bait::ObjectiveC::Project.new(path)

  app.vendor_project path, :static, source_files: project.h_files.concat(project.m_files)

We must be able to do this instead

  path = File.expand_path('../..')
  vendor_path = File.expand_path(File.join(File.dirname(__FILE__), 'vendor'))
  project = Bait::ObjectiveC::Project.new(path)

  # The next line causes 2 things:
  # dependencies are copied to vendor_path, retaining relative path therein
  # their #import directives are made to be absolute paths to the files in the vendor_path
  project.rewrite_imports :absolute, vendor_path 

  # project.source_files will just concat the h and m files behind the scenes
  app.vendor_project vendor_path, :static, source_files: project.source_files

Currently anyone can make a malicious project and push it to a known instance of bait and create their own shell or take over the box.

This should be solved by establishing a convention whereby github is pushing to a URL containing an API key.

In addition there should be basic authentication of some sort for the UI

When I click Retest on the UI, it should not just append the output. Instead I would rather persist "Runs".

Perhaps add a ToyStore#list called "test_runs" which contains the stdout and test pass result. (has_many test_runs, but its called list :test_runs, TestRun or something, see ToyStore Readme)

Then refactor build#passed? to grab the last test run and base its decision from it.

When calabash runs, it outputs a report. Just like SimpleCov, we should check and see if report/index.html exists and do all the same stuff..

It may be possible to generalize this.

Another caveat is that the only reason that report is generated, and in the report/ folder to begin with is because i've set my test.sh to run cucumber in that way, it's entirely non-standard.

Test Phase

Placing a test.sh file in your bait folder will run the "test" phase. That is all ...

Analysis Phases

Supported Languages

• CoffeeScript
• Objective-C
• Ruby
• Rails
• Javascript

(in truth, they are all supported, just write a script...) First one will be #44

Using a bait.yml file the user will order the bait phases

---
 - test.sh
 - coffeelint.sh

I should be able to get away with not having this in every script:

#!/bin/bash
bait_dir=$(dirname $0)
project_dir="$bait_dir/.."
cd $project_dir

Automatically do a chdir to eliminate the need for this.

Make sure that you can write a simple test script that will work for a rubymotion project. throw that sucker into fixtures.

Write a passing spec for unique build creation upon github webhook request.

Where else won't it run Calabash tests?

The build logs should be collapsed by default and have a "more" button to expand it

In order to prepare for a release of dependent applications (e.g. an iOS app and a Rails app)

A Project can contain multiple repositories. This is defined by the URL setup in the post-receive hook.

A Unique name will define the collection.

See the CI Workflow diagram to determine further specification

If a .bait/coffeelint.sh file exists, it will be executed as the "coffeelint" phase.

Example

$bait_dir/coffeescript
# npm install coffeelint if you dont have it, you might do this in a first priority bootstrap phase/script
File.each ...
coffeelint -f $bait_dir/config/coffeelint.json <files>
# Perhaps make this a Ruby shebang (ensure ruby in a previous script) and use https://github.com/zipcodeman/coffeelint-ruby
# it's up to the user how they want to use it

• Add Better script to README

http://stackoverflow.com/questions/3669674/streaming-data-from-sinatra-rack-application

I'm finding myself hesitating to setup bait for some of my larger ruby projects. Why? Because I'm not using RVM on this particular box.

Bait is awesome and simple as it stands right now -- but perhaps one of the first configuration options it should get is to virtualize for tests. How? Well, we have Vagrant at our disposal.

It would be pretty trivial to enable the bait server owner to flick on an option to use Vagrant.

The first step towards this ticket would probably be to use slop instead of the current Bait::CLI module, then to establish a convention for config -- at first this can just be a flag passed into bait.

This ticket is in development and might get trashed, I'm not sure yet -- but I'm definitely not comfortable running things outside of a VM in a production run of Bait.

Builds on the UI should have a retest button that will destroy the sandbox, recreate it, reclone, retest, etc.

Meaning when gem is built

This will block sinatra but that's OK for now.

When a build shows up, make it get tested automatically, the focus will now begin shifting towards RubyMotion stuff, but for now lets get it to test itself in this way.

https://github.com/blog/1227-commit-status-api

See how Travis uses this. Github does not discriminate though, anyone can use that API.

If a project has simplecov installed, a coverage/ directory will be present.
Rather than work on static analysis next, let's add simplecov support.
This will sufficiently present complications on the UI that need thought before we do static analysis.

After test, check if there was a coverage/index.html created in the sandbox
If so, set Build's boolean simplecov to true and set the URL
Publish that simplecov is available along with the URL so a button is rendered for hitting the URL

I want ansi color log output with a black background
See https://github.com/cyphactor/octopusci/blob/master/lib/octopusci/io.rb
He is using ansi2html gem: https://github.com/aslakhellesoy/ansi2html

• look good on mobile devices
• improve general design
• show commit message and sha1
• rename ref to branch and show it noiseless on 1 line ("Show more..." button)
• Add date
• Fix ugly log output

testing webhooks

use slop

bait == build and integration tester

expect the files in .bait

Deleting messes up the store. fix it