Skip to content

Conversation

@breskeby
Copy link
Contributor

Avoid eager task creation introduced lately that seems to trigger some wrong behaviour here.
Also use newer api for resolving root project

Avoid eager task creation introduced lately that seems to trigger some wrong behaviour here.
Also use newer api for resolving root project
@breskeby breskeby requested a review from a team as a code owner March 27, 2025 11:04
@breskeby breskeby added >non-issue :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team auto-backport Automatically create backport pull requests when merged v8.18.1 v8.19.0 v9.0.1 v9.1.0 v8.17.5 v8.16.7 labels Mar 27, 2025
@breskeby breskeby self-assigned this Mar 27, 2025
@elasticsearchmachine
Copy link
Collaborator

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

Copy link
Contributor

@jozala jozala left a comment

Choose a reason for hiding this comment

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

I've have one question about the recommended way of getting root project directory.
Other than that LGTM.

project.getRootProject().getPlugins().apply(GlobalBuildInfoPlugin.class);
var buildParams = loadBuildParams(project).get();

File settingsRoot = project.getLayout().getSettingsDirectory().getAsFile();
Copy link
Contributor

Choose a reason for hiding this comment

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

Is getSettingsDirectory() now a recommended way to get a project root dir?
Could project.getRootProject().getRootDir() be used here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. In general accessing other projects from a project should be avoided. Gradle is more forgiving for rootProject but still not ideal.

@breskeby breskeby merged commit b476ee1 into elastic:main Mar 27, 2025
17 checks passed
breskeby added a commit to breskeby/elasticsearch that referenced this pull request Mar 27, 2025
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.18 Commit could not be cherrypicked due to conflicts
8.x Commit could not be cherrypicked due to conflicts
9.0
8.17 Commit could not be cherrypicked due to conflicts
8.16 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 125763

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged backport pending :Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v8.16.7 v8.17.5 v8.18.1 v8.19.0 v9.0.1 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants