Skip to content

Upgrade to Gradle 6.0 #49192

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

Closed
mark-vieira opened this issue Nov 15, 2019 · 4 comments · Fixed by #49211
Closed

Upgrade to Gradle 6.0 #49192

mark-vieira opened this issue Nov 15, 2019 · 4 comments · Fixed by #49211
Assignees
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team

Comments

@mark-vieira
Copy link
Contributor

Gradle 6.0 has been released and it contains some specific items that we want in order to implement some improvements in our build such as JDK 13 support, and shared resources.

There are a number of deprecations and incompatibilities with third-party plugins, namely the ospackage plugin that will have to be resolved.

@mark-vieira mark-vieira added the :Delivery/Build Build or test infrastructure label Nov 15, 2019
@mark-vieira mark-vieira self-assigned this Nov 15, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

@mark-vieira
Copy link
Contributor Author

This is currently blocked on gradle/gradle#11426

@mark-vieira
Copy link
Contributor Author

We have a workaround in place here but I'm going to defer merging this until after the Thanksgiving holidays.

@mark-vieira
Copy link
Contributor Author

The master and 7.x branches have been updated. The workaround mentioned above has been fixed in Gradle 6.1 so should be removed after release.

@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 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 a pull request may close this issue.

2 participants