hackling/morse

A simple script that will pull down your semaphore logs and test any failed tests

morse's Issues

Setup script for Morse

A simple setup script for Morse would be nice, rather than having to make the user create a file with their token and put it in a certain place.

I think part of this would include the movement of the token file to be somewhere inside the repo, rather than the home directory.

'All tests passed' message is incorrect

There are cases on Semaphore where branches have failed but mightn't have failing tests on them, or other tests which aren't run through rspec failed, or someone stopped the build.

Perhaps a better message would be 'Unable to find any failing RSpec tests'?

Readable error message if git branch doesn't exist on Semaphore

Currently in this situation the following error message is output...

~/s/envision » morse                                                                                        ± hotfix/workforce-widget-fix-2*:97a40fe +9 11:16:06
/Users/parameme/bin/morse:81:in `find_and_cache_branch': undefined method `[]' for nil:NilClass (NoMethodError)
    from /Users/parameme/bin/morse:71:in `rescue in branch_id'
    from /Users/parameme/bin/morse:68:in `branch_id'
    from /Users/parameme/bin/morse:29:in `main'
    from /Users/parameme/bin/morse:141:in `<main>'

Cache returned data from Semaphore

Connecting to Semaphore is a bit slow at times.

It would be nice if we could have morse cache the results that it pulls down and you could run morse against those cached results.

I think doing this on a per branch basis is YAGNI, and just having one set of cached results would be fine that you could run against with morse --cached --other-options.

We should just store the output that you get from running morse without options, rather than the build log.

Clear cached branch id on 404

If there's a defined branch ID and semaphore is returning a 404 when querying status, Morse should probably clear the cached ID and fetch a new one, if the branch still isn't found then present an error.

Clear out old morse branch IDs.

When morse first finds your branch, it stores the ID so that it doesn't have to look for it again.
However, at no point do we clean that up after the branch is long gone.

Part of this could be fixing #5 and when it returns a 404, it triggers a clean, and then tries to find it again.