- Notifications
You must be signed in to change notification settings - Fork 140
Fix jruby docker images #1367
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
Fix jruby docker images #1367
Conversation
daf6cef to 68ebe05 Compare | Hi @estolfo, I was able to make the docker building work for most images, but not for This is the actual error message I get when running: cc @elastic/apm-agent-ruby, @elastic/observablt-ci |
🌐 Coverage report
|
That's likely related to the unmatch version in the current JDK and the version required by JRuby, in other words, I'd say to remove the support for Though, I don't know if that's something feasible from the support matrix, otherwise, we can remove the docker build generation for jruby-jdk7, but still be used for running the tests in the support matrix |
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, but a comment regarding the assertion
f0e7c35 to cc59359 Compare Co-authored-by: Victor Martinez <victormartinezrubio@gmail.com>
| hi @reakaleek I'm sorry I missed responding to your messages 2 weeks ago. |
| set -o pipefail | ||
| | ||
| # 7-jdk is excluded by default. See https://github.com/elastic/apm-agent-ruby/pull/1367#issuecomment-1437228929 | ||
| EXCLUDE=("7-jdk") |
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.
@estolfo regarding your question in #1367 (comment)
I did not remove it, but I excluded it by default.
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.
Ok, so does that mean the test matrix will continue to use the last created jdk7 docker image?
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, the docker image is kept in the docker registry and can still be used for tests.
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.
perfect, thanks for the explanation. LGTM then
* elastic/main: (30 commits) docs: remove kibana endpoint (elastic#1381) Update status badge (elastic#1379) Create single status check that can be set as required (elastic#1378) Remove jenkins related precommit hooks (elastic#1380) Migrate Jenkinsfile 2 GH Actions Workflow (elastic#1366) Migrate update specs to updatecli (elastic#1375) v4.6.2 Fixing Faraday::RackBuilder::StackLocked (elastic#1371) Fix jruby docker images (elastic#1367) Update reference to sinatra main (elastic#1373) Update release:update_branch task to reference branch 4.x Add missing docs reference v4.6.1 Add security options to docker containers (elastic#1356) Make sure http status code is set when Faraday Middleware is used (elastic#1368) Use composite action for updatecli workflow (elastic#1365) Fix sha source in updatecli update-specs.yml (elastic#1363) Add update-specs updatecli workflow (elastic#1359) use jruby user to run docker containers (elastic#1355) Close the read pipe at the right moment (elastic#1351) ...
Details
jruby docker image building is failing silently for an unknown time already.
This PR fixes building the docker images and exits with the correct exit codes.
Context
To run CI checks you need to do a docker login because the tests are utilising docker images hosted in
docker.elastic.co/observability-ci.However, in GH workflows created from forked PRs, we cannot access secrets.
While trying to publish the images in docker hub, I noticed that the images are failing.
How to test
Run following script. Modify Dockerfile or tests to get an error exit code.
Related Issues