CI did not build

It does not look like the build failure was related to the PR; rather, it looks like the CI job has an environment issue.

Currently under test on my z/OS system

Looks good. I ran two different jobs - one on a new workspace, one on an existing workspace with no updates. The expected messages came out correctly (repository name changed to protect the guilty):

> git --version # timeout=10
using GIT_SSH to set credentials
Using passphrase charset 'IBM1047'
> git fetch --tags --progress – git@Bitbucket.org:REPO-SLUG.git +refs/heads/:refs/remotes/origin/ # timeout=10
Checking out Revision ce210a4618766170a0dd9cc6f2aee4a8563d4070 (refs/remotes/origin/development)

and we had no authentication issues.

As a side nit - the plugin does not recognize the repository format - probably also an encoding issue but that would be a separate case.

My sincere thanks.

rsbeckerca I'm unassigning this issue from me now. I won't merge the proposed pull request until you can confirm that the entire use case is working. Keep this issue updated as you make further progress. Thanks!

markewaite We have been using the fix for a week with no issues. I can confirm that the SSH key-pair is correctly authenticating with this option. The repository format recognition is a completely separate issue and unrelated. So the entire use case is working.

Thanks. Then all I need to do is add the documentation that describes the property. That's a good excuse to document the other properties provided by the plugin as well.

rsbeckerca I've added documentation for the other properties. Does the layout look reasonable to you? If so, then I'll submit a pull request for that documentation, then once it is merged, I'll update the docs in the PR for this property.

I like the format. Actually learned something about tags that I was annoying - I want my tags being updated silently as long as they are verified. Side issue. Go for PR

Released in git client plugin 3.4.0 with the properties documented in plugin properties