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

Use the build JVM for executing third party audit checks #66379

Merged
merged 1 commit into from
Dec 15, 2020

Conversation

mark-vieira
Copy link
Contributor

We should not be using the runtime java home for build-time precommit checks. These things have no relevance to runtime java, which should only be used for changing the JVM when executing Elasticsearch code (i.e. tests), not build code. This also causes issues which certain tools because now the available classpath changes based on build environment which we don't want.

This pull request removes the last usage of runtime java home for build checks and instead we use the current Gradle JVM.

@mark-vieira mark-vieira added the :Delivery/Build Build or test infrastructure label Dec 15, 2020
@elasticmachine elasticmachine added the Team:Delivery Meta label for Delivery team label Dec 15, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@mark-vieira mark-vieira merged commit 87fafc7 into elastic:master Dec 15, 2020
mark-vieira added a commit that referenced this pull request Dec 15, 2020
mark-vieira added a commit that referenced this pull request Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants