[jbosstools-issues] [JBoss JIRA] (JBIDE-14023) investigate and make sure that openshift-java-client test get blue when testing PROD, STG and INT
[
https://issues.jboss.org/browse/JBIDE-14023?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-14023:
------------------------------------------
Clayton Coleman answered:
{quote}
Streamline has been having problems with the ticket cache getting full and overflowing
because we don't ever log out the ticket. It's possible that the volume of
automated testing against stg was a trigger for this error. It's also possibly
unrelated.
Streamline is looking at giving us an API that validates the login but does not create a
ticket. In the meantime, if you see these failures lets contact the streamline team and
check for correlation.
{quote}
To me this seems like a reasonable explanation. The 500- and auth- errors dont appear
frequently any more. Thus I'm closing this issue.
investigate and make sure that openshift-java-client test get blue
when testing PROD, STG and INT
-------------------------------------------------------------------------------------------------
Key: JBIDE-14023
URL: https://issues.jboss.org/browse/JBIDE-14023
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.1.0.Alpha2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Beta1
our matrix-test is testing openshift-java-client against PROD, INT and STG which turns
out to be very unreliable. The tests have a lot of issues which I cannot explain (server
answers with 500 "internal error", Auth errors etc.).
On the other hand there's now a test that's using a dedicated instance which runs
perfectly fine (currently blue). This integration test is included in the openshift test
which tests all openshift components:
https://ci.dev.openshift.redhat.com/jenkins/job/broker_extended/
We need to invetigate why the integration tests against PROD, STG and INT are still
unreliable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira