Tommy McNeely

Sorry, I realized I had responded to a zombie issue after I already hit submit :) Thanks, I will try that "cast" idea. Displaying all keys in the session is...

As far as "trusting" specific CA certs, I think that would be a Jenkins wide setting, and should, ideally be handled by adding the certs as trustedCertificateEntry(s) to the keystore...

Realistically, I find it _awful_ that Jenkins generates a new SSL cert each time it starts. If it would just generate an SSL cert the first time and keep using...

One of the options on the command line is `recrypt`. It feels like that would be the right place to add that functionality. (honestly, I thought that was what that...

That is the only thing I have found so far. It works fine if you specify the port on a per-server basis, but it doesn't inherit the "global" :ssh_options

@numbata: we have been using 3.4.0

Our case is very similar to the top one, trying to install SOMETHING via helm_release, and having to use a "null_resource" to wait on the VIP to properly provision. If...

I agree with the concepts of #45 and think that would make things "better" :) Even without the (extraneous) "Upgraded" message, I was thinking we should do a thread per...

Correct, my goal would be to combine all the upgrades of namespace/release-name into a single thread, instead of having to search back in the message history to find the last...

I would like to see this as well, the extra "Upgraded" notification is not very useful to us. We are using helm-operator, and generally have to watch its logs or...