-
Notifications
You must be signed in to change notification settings - Fork 1
EBP-327: updated broker image tag in the test infrastructure to the latest released 10.25.0 tag #130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
…atest released 10.25 tag
|
Please mark whether you used Copilot to assist coding in this PR
|
| nofile: | ||
| soft: 2448 | ||
| hard: 42192 | ||
| hard: 1048576 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the docs, this hard limit is required for the solace software broker version 1.25.0 to startup successfully.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✨ PR Review
LGTM
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀
|
The test suite fails to run on the Alpine linux musl node in Jenkins because the software broker fails to start up. We think it is related to the significantly higher FD required by the software broker to start up successfully. We have a solution to spin up the broker on a separate machine/node and use that remote(local) broker for our tests: this is the I will convert this PR to draft and convert it back once the allocateLocalBroker feature work has been done. |
…st 10.25.0 broker version
EBP-1204: fix the supported cipher suite list for TLSv1.2 on the latest 10.25.0 broker version
| ./test/reports/report.xml | ||
| ./test/reports/coverage.out | ||
| ./test/diagnostics.tgz | ||
| ./test/diagnostics.tgz.p7m |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the diagnostics tarball encrypted now? Can a developer extract the contents? Do we need more information for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, in the more recent versions of the broker.
| "broker_hostname": "solbroker", | ||
| "broker_container_name": "solbroker", | ||
| "broker_tag": "10.4", | ||
| "broker_tag": "10.25.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure the broker it up to release 10.25.7 now is there a strategy for rolling releases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we don't have any strategy for rolling releases. Typically, I would prefer that we upgrade the broker version on a per needs basis so we have predictive and deterministic outcomes from our integration test runs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 10.25.0 was the latest as of the time this PR was first raised.
TrentDaniel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changes:
✨ PR Description
Purpose: Update broker image tag in test infrastructure from 10.4 to 10.25.0 and adjust test timeouts for compatibility with the new version.
Main changes:
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀