Unable to build - Unknown branch "master". Push again
bhardin opened this issue · comments
I am unable to build.
When running hubot ci rooms I receive can't predict rooms now.
When running hubot ci set room REPONAME ourRoom I receive you broke everything
It looks like the problem is in /lib/janky/chat_service/hipchat.rb
error in the log:
2012-04-03T23:56:53+00:00 heroku[router]: POST sourceninja-janky.herokuapp.com/_hubot/SourceTrack/master dyno=web.1 queue=0 wait=0ms service=11ms status=404 bytes=35
2012-04-03T23:57:52+00:00 app[web.1]: ERROR: NoMethodError - undefined method `map' for nil:NilClass
2012-04-03T23:57:52+00:00 app[web.1]: app janky
2012-04-03T23:57:52+00:00 app[web.1]: method POST
2012-04-03T23:57:52+00:00 app[web.1]: user_agent
2012-04-03T23:57:52+00:00 app[web.1]: params {}
2012-04-03T23:57:52+00:00 app[web.1]: session {}
2012-04-03T23:57:52+00:00 app[web.1]: referrer
2012-04-03T23:57:52+00:00 app[web.1]: remote_ip 207.97.227.253
2012-04-03T23:57:52+00:00 app[web.1]: url http://sourceninja-janky.herokuapp.com/_github
2012-04-03T23:57:52+00:00 app[web.1]:
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/hipchat-0.4.1/lib/hipchat.rb:22:in `rooms'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service/hipchat.rb:21:in `rooms'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service.rb:81:in `rooms'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service.rb:54:in `room_id'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service.rb:34:in `default_room_id'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/repository.rb:109:in `room_id'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/branch.rb:64:in `build_for'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:26:in `handle'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:7:in `block in handle'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:5:in `each'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:5:in `handle'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/github/receiver.rb:32:in `call!'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/github/receiver.rb:18:in `call'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/builder.rb:134:in `call'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/urlmap.rb:64:in `block in call'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `each'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `call'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/exception.rb:44:in `call'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:80:in `block in pre_process'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:53:in `process'
2012-04-03T23:57:52+00:00 heroku[router]: Error H13 (Connection closed without response) -> POST sourceninja-janky.herokuapp.com/_github dyno=web.1 queue= wait= service= status=503 bytes=
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:86:in `start'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/runner.rb:185:in `run_command'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/runner.rb:151:in `run!'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/bin/thin:6:in `<top (required)>'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/bin/thin:19:in `load'
2012-04-03T23:57:52+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/bin/thin:19:in `<main>'
We were using a notification token in Hipchat. The token you create needs to be an admin token.
The hipchat gem doesn't catch 401 authorization errors. It assumes it worked.
I had this working, but because of issue #66 tried to move the server, thinking it was something with the initial DB setup.
I am now getting the following error when pushing to the repo or testing the hook from github:
2012-04-09T23:51:28+00:00 app[web.1]: ERROR: NoMethodError - undefined method `map' for nil:NilClass
2012-04-09T23:51:28+00:00 app[web.1]: app janky
2012-04-09T23:51:28+00:00 app[web.1]: method POST
2012-04-09T23:51:28+00:00 app[web.1]: user_agent
2012-04-09T23:51:28+00:00 app[web.1]: params {}
2012-04-09T23:51:28+00:00 app[web.1]: session {}
2012-04-09T23:51:28+00:00 app[web.1]: referrer
2012-04-09T23:51:28+00:00 app[web.1]: remote_ip 50.57.128.197
2012-04-09T23:51:28+00:00 app[web.1]: url http://sourceninja-janky2.herokuapp.com/_github/
2012-04-09T23:51:28+00:00 app[web.1]:
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/hipchat-0.4.1/lib/hipchat.rb:22:in `rooms'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service/hipchat.rb:21:in `rooms'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service.rb:81:in `rooms'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service.rb:54:in `room_id'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/chat_service.rb:34:in `default_room_id'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/repository.rb:109:in `room_id'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/branch.rb:64:in `build_for'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:26:in `handle'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:7:in `block in handle'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:5:in `each'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/build_request.rb:5:in `handle'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/github/receiver.rb:32:in `call!'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/github/receiver.rb:18:in `call'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/builder.rb:134:in `call'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/urlmap.rb:64:in `block in call'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `each'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `call'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.11/lib/janky/exception.rb:44:in `call'
2012-04-09T23:51:28+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/connection.rb:80:in `block in pre_process'
Please help?
Problem was still the same with the token. Our old configuration script had the old JANKY_CHAT_HIPCHAT_TOKEN. Once you create the token, you can't change it to an admin token, you need to delete it and create a new one. The new token_id that we created was not in our build script.
If you run into this problem, verify that your JANKY_CHAT_HIPCHAT_TOKEN is an admin token.