You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an exisiting Jenkins instance (2.289.3) with 1.21 installed, which runs this plugin with a stored Global credential (SSH keypair) and is able to connect to the SSH host just fine.
As an upgrade path in progress we also have a new Jenkins instance (2.452.2) running 1.25 with the same setup, on which the plugin fails to connect, unless I enter the key directly in the Publish over SSH config, even though it's configured identical in a Global credential.
So I think that somewhere between versions 1.21 and 1.25 the Jenkins credential provider is not used anymore, requiring credentials to be entered directly in the 'Publis over SSH' configuration. Is that a correct assumption or am I missing something completely obvious?
I have searched online for this problem and the only info I found was this issue: #70
So, is this a feature or a bug? And if it's a bug, is there any update on fixing it?
The text was updated successfully, but these errors were encountered:
I understand from #70 (comment) that it is a bug which still needs to be fixed.
So to make it work on the new version, I'll configure the SSH key for each node seperately.
Hi,
We have an exisiting Jenkins instance (2.289.3) with 1.21 installed, which runs this plugin with a stored Global credential (SSH keypair) and is able to connect to the SSH host just fine.
As an upgrade path in progress we also have a new Jenkins instance (2.452.2) running 1.25 with the same setup, on which the plugin fails to connect, unless I enter the key directly in the Publish over SSH config, even though it's configured identical in a Global credential.
So I think that somewhere between versions 1.21 and 1.25 the Jenkins credential provider is not used anymore, requiring credentials to be entered directly in the 'Publis over SSH' configuration. Is that a correct assumption or am I missing something completely obvious?
I have searched online for this problem and the only info I found was this issue: #70
So, is this a feature or a bug? And if it's a bug, is there any update on fixing it?
The text was updated successfully, but these errors were encountered: