rotten
rotten copied to clipboard
DTrejo
quits with no logging
David,
Any idea why this isn't working? I get no logging.
tiny:~/voxer/server$ (release) rotten -p release
Running against /Users/kip/voxer/server
Checking that branches are in production branch release
....................................tiny:~/voxer/server$ (release)
— @rv-kip
@rv-kip try this with the newest version of rotten from npm? I've just updated it to print more error output. TY!
No dice. It is worse now.
$ rotten -p release
Running against /voxer/server
Checking that branches are in production branch release
undefined
Please report bugs to https://github.com/dtrejo/rotten, thank you.
I accidentally published a broken version, would you mind doing
npm rm rotten; npm cache clean rotten; npm -g install rotten
Thank you and sorry for releasing broken code!
On Tue, Sep 11, 2012 at 4:37 PM, Kip Gebhardt [email protected]:
No dice. It is worse now.
$ rotten -p release Running against /voxer/server Checking that branches are in production branch release
undefined Please report bugs to https://github.com/dtrejo/rotten, thank you.
— Reply to this email directly or view it on GitHubhttps://github.com/DTrejo/rotten/issues/2#issuecomment-8471809.
See my projects at dtrejo.com
Works great! Thanks.
On Tue, Sep 11, 2012 at 8:01 PM, David Trejo [email protected]:
I accidentally published a broken version, would you mind doing
npm rm rotten; npm cache clean rotten; npm -g install rotten
Thank you and sorry for releasing broken code!
On Tue, Sep 11, 2012 at 4:37 PM, Kip Gebhardt [email protected]:
No dice. It is worse now.
$ rotten -p release Running against /voxer/server Checking that branches are in production branch release
undefined Please report bugs to https://github.com/dtrejo/rotten, thank you.
— Reply to this email directly or view it on GitHub< https://github.com/DTrejo/rotten/issues/2#issuecomment-8471809>.
See my projects at dtrejo.com
— Reply to this email directly or view it on GitHubhttps://github.com/DTrejo/rotten/issues/2#issuecomment-8479924.
@DTrejo I am getting the "quit with no logging" error again
$ (release) rotten -p release
Running against /voxer/server
Checking that branches are in production branch release
..........................................................................................................................Please report bugs to https://github.com/dtrejo/rotten, thank you.
Node v0.8.7
:(
Maybe I will clone the linux kernel repo and see if I can reproduce this. May be a while before I get to it though, sorry.
Damn... the linux repo on github at least does not have any remote branches...
Pushing an update anyway I suppose.
Please let me know if this fixes the problem kip! (Or at least gives informative error messages).
Cheers, D