Skip to content
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

Build action #3

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Build action #3

wants to merge 5 commits into from

Conversation

tombueng
Copy link

Please add a build action so we can download your extensoin from github.

<repository>
<id>github</id>
<name>GitHub Packages</name>
<url>https://maven.pkg.github.com/tombueng/spring-otel-extended</url>
Copy link
Author

Choose a reason for hiding this comment

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

Needs to be adjusted!

working-directory: otel-javaagent-spring-extension
steps:
- uses: actions/checkout@v4
- name: Set up JDK 11
Copy link
Owner

Choose a reason for hiding this comment

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

Shuoldn't this be called 21?

@DGuhr
Copy link
Owner

DGuhr commented Oct 30, 2024

@tombueng Thank you for your contribution first of all. Unexpected :)
That said: The build in this PR is using jdk 21. This opens up a question: The reason why I did not add a build action in the first place (apart from me being lazy) is, that you have to build it yourself with the java version matching your applications' java version. So, when you run a JDK 11 java app/otel agent, but build the extension with JDK 21, it won't work - see my notes in the README. So i think if we want to add a build/release step here, we should have at least a matrix build for, say, last three JDK LTE versions + current one, right? So it's not that simple. I'm happy to hear your thoughts about this, not at all against adding it, but if we add it, it should be right not just for one use case, but in general.

edit: added #4 as issue for this.

@DGuhr DGuhr mentioned this pull request Oct 30, 2024
@DGuhr DGuhr linked an issue Oct 30, 2024 that may be closed by this pull request
@tombueng
Copy link
Author

tombueng commented Oct 30, 2024 via email

@tombueng
Copy link
Author

tombueng commented Oct 30, 2024 via email

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.

Add a build/release step
2 participants