Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Add new env variable to set wsagent ping success threshold #475

Conversation

l0rd
Copy link
Contributor

@l0rd l0rd commented Dec 7, 2017

Copy link
Member

@ibuziuk ibuziuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving, but we should be careful with merging this one - cms on prod / prod-preview should be updated first. Otherwise the deployment would fail

@ibuziuk
Copy link
Member

ibuziuk commented Dec 7, 2017

I have created GitLab issue https://gitlab.cee.redhat.com/dtsd/housekeeping/issues/946

Signed-off-by: Mario Loriedo <mario.loriedo@gmail.com>
@l0rd l0rd force-pushed the wsagent-ping-success-threshold branch from 7914ee3 to 2b6b892 Compare December 7, 2017 16:32
@l0rd
Copy link
Contributor Author

l0rd commented Dec 7, 2017

Cool thanks @ibuziuk I have also included the change to the pom.xml in this PR so we should wait for a new upstream fix release.

@l0rd l0rd merged commit d2c1e5d into redhat-developer:multi-tenant-rh-che Dec 7, 2017
@l0rd l0rd deleted the wsagent-ping-success-threshold branch December 7, 2017 23:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants