feat: download opentelemetry jar outside of Dockerfile #697
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Downloads the OpenTelemetry Agent jar "outside" of the Dockerfile. This is actually done in two locations:
build.gradle.kts
file: a Gradle task is added for thispublish-docker-image
action: a GH Actions step is added, because when publishing we don't use the Gradle Docker taskWHY
Downloading the OTEL Agent inside Docker required adding
curl
first, and due to security restrictions that required a fixed version. APK, Alpine Linux's package manager, seems to not keep older versions around, which caused the build to break whenever a new version ofcurl
was released.FURTHER NOTES
opentelemetry-javaagent.jar
once per project, directly to each project'sbuild/
folder.Closes #686