It would be nice, if it were possible to have one set of jobs that could build a change on master or 4.2.x.
Problems being, I'm not sure how the polling for changes / sparse checkout would handle this for each branch. ie. how does a job get triggered, and pass the branch to the param build?