Special case NoRemoteRepository during replication
If the remote repository doesn't exist, we only need to know what
URL was accessed, not a full Java stack trace. The issue will be
a simple configuration problem for the administrator, and having
that stack trace in place just confuses things.
Signed-off-by: Shawn O. Pearce <sop@google.com>
diff --git a/src/main/java/com/google/gerrit/git/PushQueue.java b/src/main/java/com/google/gerrit/git/PushQueue.java
index c69da42..a953a9a 100644
--- a/src/main/java/com/google/gerrit/git/PushQueue.java
+++ b/src/main/java/com/google/gerrit/git/PushQueue.java
@@ -23,6 +23,7 @@
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
+import org.spearce.jgit.errors.NoRemoteRepositoryException;
import org.spearce.jgit.errors.NotSupportedException;
import org.spearce.jgit.errors.TransportException;
import org.spearce.jgit.lib.NullProgressMonitor;
@@ -168,6 +169,9 @@
final PushResult res;
try {
res = tn.push(NullProgressMonitor.INSTANCE, cmds);
+ } catch (NoRemoteRepositoryException e) {
+ log.error("Cannot replicate to " + op.uri + "; repository not found");
+ return;
} catch (NotSupportedException e) {
log.error("Cannot replicate to " + op.uri, e);
return;