Skip to content

Some HTTP calls to jenkins result in a 302, which currently throws an HttpResponseException #7

Closed

Description

Oops - this is probably a fault in my latest patch. I will work on a solution soon, but for now the client can work around it by simply catching the exception and checking the response code to see if it is 302.

Example stacktrace:

[INFO] [talledLocalContainer] 2013-06-03 17:11:48,015 ERROR [AtlassianEvent::pool-3-thread-5] admin 1031x221x1 1b4iha6 127.0.0.1 "POST /scm/project_1/rep_1.git/git-receive-pack HTTP/1.1" c.p.s.s.managers.JenkinsManager HTTP Error (resp code 302
[INFO] [talledLocalContainer] org.apache.http.client.HttpResponseException: Found
[INFO] [talledLocalContainer]   at com.offbytwo.jenkins.client.JenkinsHttpClient.post(JenkinsHttpClient.java:142) ~[stashbot-helper-1.0-SNAPSHOT_1370304253000.jar:na]
[INFO] [talledLocalContainer]   at com.offbytwo.jenkins.model.Job.build(Job.java:58) ~[stashbot-helper-1.0-SNAPSHOT_1370304253000.jar:na]
[INFO] [talledLocalContainer]   at <my code here>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions