PushCommand: do not set a null credentials provider
PushCommand now does not set a null credentials provider on Transport because in this case the default provider is replaced with null and the default mechanism for providing credentials is not working. Bug: 336023 Change-Id: I7a7a9221afcfebe2e1595a5e59641e6c1ae4a207 Signed-off-by: Jens Baumgart <jens.baumgart@sap.com>
This commit is contained in:
parent
b0245b548b
commit
29ed09a44f
|
@ -139,6 +139,7 @@ public Iterable<PushResult> call() throws JGitInternalException,
|
|||
if (receivePack != null)
|
||||
transport.setOptionReceivePack(receivePack);
|
||||
transport.setDryRun(dryRun);
|
||||
if (credentialsProvider != null)
|
||||
transport.setCredentialsProvider(credentialsProvider);
|
||||
|
||||
final Collection<RemoteRefUpdate> toPush = transport
|
||||
|
|
Loading…
Reference in New Issue