Increase deployment config timeout to 3600s
that's for a RollingUpdate and intended to compensate long image download times on slow networks.
Please follow the discussion on for more about this default values.
Is related to and supersedes it.
@@ -174,8 +174,17 @@ public class ResourceMojo extends AbstractResourceMojo {
* The OpenShift deploy timeout in seconds:
* See this issue for background of why for end users on slow wifi on their laptops
* DeploymentConfigs usually barf: https://github.com/openshift/origin/issues/10531
+ *
+ * Please follow also the discussion at
+ * <ul>
+ * <li>https://github.com/fabric8io/fabric8-maven-plugin/pull/944#discussion_r116962969</li>
+ * <li>https://github.com/fabric8io/fabric8-maven-plugin/pull/794</li>
+ * </ul>
+ * and the references within it for the reason of this ridiculous long default timeout
+ * (in short: Its because Docker image download times are added to the deployment time, making
+ * the default of 10 minutes quite unusable if multiple images are included in the deployment).
*/
- @Parameter(property = "fabric8.openshift.deployTimeoutSeconds")
+ @Parameter(property = "fabric8.openshift.deployTimeoutSeconds", defaultValue = "3600")
private Long openshiftDeployTimeoutSeconds;
// Access for creating OpenShift binary builds
@@ -185,9 +194,6 @@ public class ResourceMojo extends AbstractResourceMojo {
private OpenShiftDependencyResources openshiftDependencyResources;
- public ResourceMojo() {
- }
-
public void executeInternal() throws MojoExecutionException, MojoFailureException {
clusterAccess = new ClusterAccess(namespace);
try {
