Skip to content

PoC for jib#5870

Closed
taer wants to merge 2 commits into
opensearch-project:mainfrom
taer:taer-patch-1
Closed

PoC for jib#5870
taer wants to merge 2 commits into
opensearch-project:mainfrom
taer:taer-patch-1

Conversation

@taer
Copy link
Copy Markdown

@taer taer commented Jul 2, 2025

Description

[Describe what this change achieves]

Issues Resolved

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Robert Macaulay <robert.macaulay@gmail.com>
@taer taer mentioned this pull request Jul 2, 2025
4 tasks
@taer
Copy link
Copy Markdown
Author

taer commented Jul 2, 2025

looks like the failed test was where it checked out main, not my branch. There is no dockerPrepare in the project anymore, so I'm not sure what that's doing.

@dlvenable
Copy link
Copy Markdown
Member

Thank you @taer for experimenting with this. I'm not very familiar with jib, so I'll try to look into that a little more.

One think to take note of is that we do use Docker to build the end-to-end tests. Data Prepper has a small set of end-to-test tests to verify certain behaviors. To run the tests, they do two things:

  1. For JVM-based tests (ie. test against Java 11, 17, 21), the tests build a custom Docker image using that specific Java version.
  2. For the Docker test, it uses the actual release Docker image that you removed.

See this project:

https://github.com/opensearch-project/data-prepper/blob/c94eeee93d220000c721c6dc5627ddf37c12b57f/e2e-test/build.gradle

We would need to update at least the Docker test to use the jib build.

Also, could we move the jib build into release/docker to keep it from being needed for all main builds?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

}


jib {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It would be nice to use jib only from the :release:docker project. Is that possible?

*/

plugins {
id 'com.palantir.docker' version '0.35.0'
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This would also help since this plugin is now deprecated. So using job would resolve #5313 as well.

@taer
Copy link
Copy Markdown
Author

taer commented Aug 14, 2025

Just following up. I've been swamped. I managed to stand it up on amd64s, and now have been pulled in 4 different directions. I'll see if I can revisit this soon

@dlvenable
Copy link
Copy Markdown
Member

@taer ,

Data Prepper now supports Docker images which is what I believe this was aiming to support. I'm going to close this. If you believe it is still needed, please open an issue or a new PR.

@dlvenable dlvenable closed this May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants