Make new timeout property usable in free-style jobs and add it to doc - #294
Conversation
|
@ogulcanaydogan could you please review this? |
4c5592a to
e2c5f41
Compare
ogulcanaydogan
left a comment
There was a problem hiding this comment.
Thanks for picking this up, having the timeout on freestyle jobs too makes sense.
One thing before it actually works: the @DataBoundConstructor drops the timeout. It calls this(CredentialHolder.toIdList(credentialHolders), ignoreMissing), which routes to the deprecated (List<String>, boolean) overload, and that one fills in DEFAULT_TIMEOUT_MINUTES. So whatever the user types in the field never reaches this.timeout, it stays at 1. Passing it through fixes it:
this(CredentialHolder.toIdList(credentialHolders), ignoreMissing, timeout);Smaller note: the new timeout field/getter is @since 405, but 405 already shipped on Jul 22 without it, so this one is the next release (@since FIXME like #286 did). The FIXME to 405 changes on the ExecRemoteAgent side are right, that code did land in 405.
e2c5f41 to
a866f51
Compare
Oh yes, I missed that. Thanks for pointing out. Fixed it (as suggested).
Yes. I wanted to be a bit 'lazy' and avoid subsequent changes by using the version where the timeout feature generally became available. But changed it as you suggested. |
ogulcanaydogan
left a comment
There was a problem hiding this comment.
Nice, thanks for the quick fix. The DataBoundConstructor threads the timeout through now, and the @since split reads right (FIXME for the freestyle field, 405 for the ExecRemoteAgent bits that already shipped). Good call extending the timeout to freestyle jobs too, that was a real gap. Approving, thanks!
|
Great, thanks for your reviews. Can this and my other ready/approved PR thru be submitted? |
|
Happy to land all three! Since they overlap in |
Add a timeout field to the SSHAgentBuildWrapper to make it usable in freestyle jobs, too.
a866f51 to
6dfde48
Compare
Add a timeout field to the SSHAgentBuildWrapper to make it usable in freestyle jobs, too.
Follow-up on
Personally I'm not using freestyle jobs, but for completes and feature parity, I think this would be good.
Testing done
Submitter checklist