Pass reference to cloud and job for better cause of blockage

Author: patbos

src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesQueueTaskDispatcher.java

@@ -19,16 +19,25 @@ public CauseOfBlockage canTake(Node node, Queue.BuildableItem item) {
             KubernetesSlave slave = (KubernetesSlave) node;
             Task ownerTask = item.task.getOwnerTask();
             if (!KubernetesFolderProperty.isAllowed(slave, (Job) ownerTask)) {
-                return new KubernetesCloudNotAllowed();
+                return new KubernetesCloudNotAllowed(slave.getKubernetesCloud(), (Job) ownerTask);
             }
         }
         return null;
     }
 
     public static final class KubernetesCloudNotAllowed extends CauseOfBlockage {
+
+        private final KubernetesCloud cloud;
+        private final Job job;
+
+        public KubernetesCloudNotAllowed(KubernetesCloud cloud, Job job) {
+            this.cloud = cloud;
+            this.job = job;
+        }
+
         @Override
         public String getShortDescription() {
-            return Messages.KubernetesCloudNotAllowed_Description();
+            return Messages.KubernetesCloudNotAllowed_Description(cloud.name, job.getFullName());
         }
     }
 }

src/main/resources/org/csanchez/jenkins/plugins/kubernetes/Messages.properties

@@ -8,4 +8,4 @@ KubernetesSlave.HomeWarning=[WARNING] HOME is set to / in the jnlp container. Yo
     troubles when using tools or ssh client. This usually happens if the uid doesn't have any \
     entry in /etc/passwd. Please add a user to your Dockerfile or set the HOME environment \
     variable to a valid directory in the pod template definition.
-KubernetesCloudNotAllowed.Description=Kubernetes cloud is not allowed for folder
+KubernetesCloudNotAllowed.Description=Kubernetes cloud {0} is not allowed for folder containing job {1}