"Unknown branch" + "Shit's being weird" messages when building

Question

"Unknown branch" + "Shit's being weird" messages when building

juandazapata opened this issue 13 years ago · comments

"Unknown branch" and "Shit's being weird"

When
me -> hubot ci setup $organization/$repo
It creates the build task in Jenkins correcty and outputs the work.

When
me -> hubot ci build $repo
hubot -> Unknown branch "master". Push again
hubot -> Can't go HAM on web/master, shit's being weird.

When
me -> hubot ci status $repo/$branch
Doesn't return anything

When
me -> hubot ci status
hubot -> $repo no build Publishing git@github.com:$organization/$repo

Our IT

Hubot on Heroku
Janky on Heroku
Jenkins on Cloudbees

Any thoughts?

Simon Rozet · Answer 1 · Wed Jan 04 2012 05:47:33 GMT+0800 (China Standard Time)

Anything in heroku logs? Hopefully there's a stacktrace in there.

richö butts · Answer 2 · Wed Jan 04 2012 12:46:19 GMT+0800 (China Standard Time)

Have you pushed since?

Juanda · Answer 3 · Wed Jan 04 2012 23:29:07 GMT+0800 (China Standard Time)

@richoH Yes, I've pushed several times.
@sr Heroku logs tells me this

2012-01-04T15:08:09+00:00 app[web.1]: TypeError - can't convert nil into String:
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/cookie.rb:152:in `hexdigest'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/cookie.rb:152:in `generate_hmac'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/cookie.rb:109:in `unpacked_cookie_data'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:43:in `load_session_id!'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/cookie.rb:99:in `extract_session_id'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:32:in `[]'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:262:in `current_session_id'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:268:in `session_exists?'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:107:in `exists?'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:122:in `load_for_read!'
2012-01-04T15:08:09+00:00 app[web.1]:   /app/vendor/bundle/ruby/1.9.1/gems/rack-1.4.0/lib/rack/session/abstract/id.rb:64:in `has_key?'

However the JANKY_SESSION_SECRET is setted up.

Any ideas?

Simon Rozet · Answer 4 · Wed Jan 04 2012 23:39:12 GMT+0800 (China Standard Time)

@juandazapata Is that when hitting the dashboard? Receiving a post-receive hook from GitHub shouldn't involve any session business. Maybe try to tail the log with heroku logs -t and hit "Test Hook" in on GitHub.

Juanda · Answer 5 · Thu Jan 05 2012 23:25:25 GMT+0800 (China Standard Time)

@sr I'm not getting the TypeError - can't convert nil into String: anymore.

However it's still not working...when I hit "Test Hook" the log says:
2012-01-05T15:24:27+00:00 heroku[router]: Error H13 (Connection closed without response) -> POST janky.herokuapp.com/_github dyno=web.1 queue= wait= service= status=503 bytes=

Juanda · Answer 6 · Thu Jan 05 2012 23:33:57 GMT+0800 (China Standard Time)

Also I noticed that my Hubot logs says this when I run hubot ci status repo/branch:

2012-01-05T15:30:18+00:00 app[app.1]: [Thu, 05 Jan 2012 15:30:18 GMT] ERROR Campfire error: 422

Simon Rozet · Answer 7 · Fri Jan 06 2012 22:41:59 GMT+0800 (China Standard Time)

@juandazapata The heroku[router] error means the app is throwing an exception. You should see something similar to the TypeError - can't convert nil into String error you were getting earlier.

The hubot error is probably unrelated.

Juanda · Answer 8 · Sat Jan 07 2012 00:16:55 GMT+0800 (China Standard Time)

@sr Just after a git push I see the following on the Janky log:

2012-01-06T16:13:43+00:00 heroku[router]: Error H13 (Connection closed without response) -> POST janky.herokuapp.com/_hubot/repo/branch dyno=web.1 queue= wait= service= status=503 bytes= 2012-01-06T16:13:43+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/janky-0.9.0/lib/janky/build.rb:105:in 'rerun'

Simon Rozet · Answer 9 · Sat Jan 07 2012 00:35:26 GMT+0800 (China Standard Time)

Double check the JANKY_BUILDER_DEFAULT setting. It should look something like this: http://user:password@jenkins-ip. Are you on IRC maybe? Should be easier to debug things on IM.

Juanda · Answer 10 · Sat Jan 07 2012 00:44:17 GMT+0800 (China Standard Time)

@sr Yes, the JANKY_BUILDER_DEFAULT is correct.
Let's chat over IRC, I'm on FreeNode on the #jenkins room (juanda)

Jesse Angell · Answer 11 · Fri Jan 13 2012 13:29:51 GMT+0800 (China Standard Time)

I'm having the same problem and it being solved over IRC isn't going to be of much help.. What was the problem?

Simon Rozet · Answer 12 · Sun Jan 15 2012 04:51:13 GMT+0800 (China Standard Time)

JANKY_BUILDER_DEFAULT was missing a trailing slash