escape repository on command line
Update composer.lock
Update composer.lock (HttpKernel commit id)
merged branch smaftoul/patch-1 (PR #60)

Commits
-------

ebe0cc2 Update composer.lock (HttpKernel commit id)
721e2ed Update composer.lock

Discussion
----------

Correct composer.lock

Unit tests passed
add SSHProject
merged branch havvg/feature/ssh-project (PR #62)

Commits
-------

9843a31 add SSHProject

Discussion
----------

add SSHProject

see #49 and #20
merged branch havvg/hotfix/escape-repository (PR #55)

Commits
-------

83e79bc escape repository on command line

Discussion
----------

escape repository on command line

This is required to have e.g. local repositories with spaces in their directory path working.

---------------------------------------------------------------------------

by cordoval at 2012-03-22T20:33:45Z

interesting i wonder why it was not escaped before, I mean, is there a special reason for that?

other than that this is ready for merge

---------------------------------------------------------------------------

by havvg at 2012-03-22T20:41:14Z

No special reason, I just missed it there and while testing it, it didn't cause errors on the test setup.

---------------------------------------------------------------------------

by cordoval at 2012-03-22T20:45:52Z

then if you add this escape i suggest by tdd add the corresponding tests, otherwise there is no justification for the code :D

---------------------------------------------------------------------------

by havvg at 2012-03-22T20:49:02Z

As by TDD, the one who wrote the code should not write the tests, that's why it happened in the first place, soo .. go ahead! :P

---------------------------------------------------------------------------

by cordoval at 2012-03-22T20:50:07Z

ok I will PR but give me some time please, let me practice :D
added static default command to Sismo\Project
merged branch havvg/feature/default-build-command (PR #30)

Commits
-------

7055f40 added static default command to Sismo\Project

Discussion
----------

add static default command to Sismo\Project

This allows to alter the default command for all newly created projects with just one line.

It's meant to be used in the config.file of Sismo to (for example) change the default options of the phpunit command to run or even change the test suite to run at all.

Example:

```php
<?php

$projects = array();
$notifier = new Sismo\GrowlNotifier('pa$$word');

\Sismo\Project::setDefaultCommand('phpunit --colors --strict');

$projects[] = new Sismo\GithubProject('Twig (Local)', '/Users/fabien/Twig', $notifier);
$projects[] = new Sismo\GithubProject('Twig', 'fabpot/Twig', $notifier);

return $projects;
```

---------------------------------------------------------------------------

by cordoval at 2011-09-24T01:09:47Z

I think this is the same problem I had, to change commands for the types of testings that I am currently doing, however @fabpot told me that we can call a generic script that can sit on the project folder of the git project? so I am trying to figure out how to do that, any hints? So this approach is better than touching the config.php, I say config.php should only be touched to add projects but not commands, like the apache sites file, only once

---------------------------------------------------------------------------

by cordoval at 2011-09-24T01:12:04Z

@havvg now I know this will never be merged as sismo is by definition tool agnostic and for the above reasons I posed.

I say @fabpot would do well in showing that sample of script he referred to, but for now I am thinking on its shape, sismo rocks!

---------------------------------------------------------------------------

by havvg at 2011-09-24T09:31:06Z

Yes I know.

However, I think it's worth to have something to alter the default command of Sismo instead of having the same three lines for every project configuration.

---------------------------------------------------------------------------

by cordoval at 2011-09-24T14:05:05Z

I agree too

---------------------------------------------------------------------------

by cordoval at 2011-09-24T20:14:13Z

hey @havvg, do you have gmail, add me to brainstorm sometime, I have an idea

I was successful in extracting a script into each project folder so that the command could be customized right on a file inside the project folder. Like I have extracted the What I think would be good to automate is to extract also the part of the configuration for each project. Wonder if @fabpot has done this already... so the scenario is like this:

we all have main folder web/ or sites/ where we put all our apps and map them to vhosts

so sismo perhaps can scan from the config.php a particular main folder $appsFolder and read inside a standard sismo_config.php per project, inside each there is the setup for the $project at hand and so that it can be inserted back into the closure project array or something ...

makes sense? It should be easy to implement but I am looking for better ideas because i do my mess.

Thanks!

---------------------------------------------------------------------------

by havvg at 2011-09-26T15:54:56Z

You already can do this with the given sismo config.file.

You only need to fill it with the list of projects to look into and the base logic for loading the expected file within each project.

---------------------------------------------------------------------------

by cordoval at 2011-09-26T16:15:08Z

what do you mean 'base logic' ...

---------------------------------------------------------------------------

by havvg at 2011-09-26T17:22:15Z

Actually, your idea is pretty cool, need to implement it. I will do this tomorrow and post the code!

---------------------------------------------------------------------------

by cordoval at 2011-09-26T17:26:25Z

glad to be understood :) yeah man, let me knwo I will be on the chat all day long

---------------------------------------------------------------------------

by havvg at 2011-09-26T17:28:58Z

Code will be there: https://github.com/havvg/SismoFinder

---------------------------------------------------------------------------

by cordoval at 2011-09-26T17:30:04Z

allow permissions to push, perhaps with this pace, I won't want to wait till tomorrow

---------------------------------------------------------------------------

by havvg at 2011-09-26T17:36:55Z

Done.

---------------------------------------------------------------------------

by havvg at 2012-01-04T19:41:19Z

@fabpot What are your thoughts on this PR?

---------------------------------------------------------------------------

by havvg at 2012-04-19T14:33:14Z

Rebased onto current master
Proposed a new notifier called WallpaperNotifier

This notifier uses the wallpaper to notify build results.
It was awarded as the most useful notifier in the ibuildings Sismo
Challenge. Details:
http://techportal.ibuildings.com/2012/04/17/sismo-challenge-results/

Details about the notifier and how to use it:
http://www.slideshare.net/javier.eguiluz/wallpaper-notifier
merged branch javiereguiluz/master (PR #63)

Commits
-------

99388d7 Proposed a new notifier called WallpaperNotifier

Discussion
----------

Proposed a new notifier called WallpaperNotifier

This notifier uses the wallpaper to notify build results.

It was awarded as the most useful notifier in the ibuildings Sismo Challenge. Details: http://techportal.ibuildings.com/2012/04/17/sismo-challenge-results/

Details about the notifier and how to use it:
http://www.slideshare.net/javier.eguiluz/wallpaper-notifier