-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[CI] Remove UBI docker acceptance test #17828
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
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
This pull request does not have a backport label. Could you fix it @kaisecheng? 🙏
|
hmm, something must have changed in the UBI image? If that base image is setting |
Also, is it expected that we run the trim task for containers other than observability SRE? |
Not seeing it set in the ubi base
|
Since v9, the full / default image use UBI as base image, so "full flavour acceptance" has covered UBI in main. The failures are from all docker test, which is mapped to "ubi flavour acceptance". I think we should clean up UBI from exhaustive test for main and v9 For v8, the "full" use Ubuntu as base image and UBI flavour is still available. |
rakelib/plugin.rake
Outdated
# https://github.com/elastic/logstash/pull/17125 | ||
next false if line.match?(/^Using (system java|bundled JDK|LS_JAVA_HOME defined java)/) | ||
|
||
next false if line.match?(/pass JVM parameters via LS_JAVA_OPTS/) |
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.
If this warning is being printed, that means the environment has a legitimate issue IMO. JAVA_HOME
should not be set, if it is somewhere in our build process (or even worse our final container artifacts) we should find that and fix it. Ignoring it here seems to be papering over a real problem.
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 issue is not related to JAVA_HOME, but rather to JAVA_OPTS
I don't think any base image set JAVA_OPTS. It is the project bash script running in some repeated way in "all docker tests" and set the JAVA_OPTS, probably here
Maybe "all docker tests" was part of the CI in the past, but it is not anymore.
Just confirmed the CI has passed the failing point by removing this line. But I am going to revert it, because UBI test should be removed
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.
Sorry, i meant JAVA_OPTS
that was a typo, i was also looking at JAVA_HOME
for something else 🤦
The ubi removal makes sense!
Waiting CI to be green https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/2122 |
|
💚 Build Succeeded
History
|
@Mergifyio backport 9.0 9.1 |
✅ Backports have been created
|
This commit removes the UBI acceptance test. The default base image is UBI. Full flavour test has covered UBI flavour Fixes: #17830 (cherry picked from commit f4c195c) Co-authored-by: kaisecheng <[email protected]>
This commit removes the UBI acceptance test. The default base image is UBI. Full flavour test has covered UBI flavour Fixes: #17830 (cherry picked from commit f4c195c) Co-authored-by: kaisecheng <[email protected]>
This commit removes the UBI acceptance test.
The default base image is UBI. Full flavour test has covered UBI flavour
Fixes: #17830
This commit removes the unwanted warning which pollutes the plugins listinstalled_plugins is polluted with ["pass JVM parameters via LS_JAVA_OPTS", "logstash-codec-avro", "logstash-codec-cef", ... ]