JobsApi.build() error messages are not reported

Expected Behavior

When launching a build with an invalid build name, errors reported by Jenkins should be passed along to the caller.

Current Behavior

When launching a build with an invalid build name, a null Integer is returned.

Context

When an invalid build name is passed, there is no indication as to what was wrong other than null being returned. This forces users to setup logging and re-run the program, something most end users find difficult to do and/or too costly.

As suggested in comment https://github.com/cdancy/jenkins-rest/issues/14#issuecomment-387248721 it probably makes sense to return a RequestStatus response rather than a plain integer.

Steps to Reproduce (for bugs)

The following groovy code reproduces the problem:

@Grab(group='com.cdancy', module='jenkins-rest', version='0.0.8')
import com.cdancy.jenkins.rest.JenkinsClient
JenkinsClient client = JenkinsClient.builder().build()
println(client.api().jobsApi().build("non-existent"))

It will print: null and there is no error message.

Your Environment

Linux command line.

[martinda]

I am attempting an implementation of IntegerResponse on this branch. I am not done, three tests are failing and I am debugging.

[martinda]

Can you explain the difference you are making between a ResponseWrapper and an IntegerResponse, for example you say that IntegerResponse would be more generic than ResponseWrapper, what do you mean by that (I would have thought the other way around)?