fix(gradle): enforce that only one gradle task can be passed into gradle executor#34269
Merged
FrozenPandaz merged 1 commit intomasterfrom Feb 2, 2026
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit b1988f3
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
approved these changes
Feb 2, 2026
FrozenPandaz
pushed a commit
that referenced
this pull request
Feb 3, 2026
…dle executor (#34269) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> The Gradle executor accepts a taskName option that *should not* contain multiple space-separated tasks. When multiple tasks are provided, the batch runner misinterprets the space-separated string as containing project names rather than treating it as a single task argument, leading to execution errors and confusion. This only occurs if the taskName is manually overridden and should not occur when task names are generated by the project graph plugin. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> The Gradle executor now validates that taskName contains only a single task without spaces. If multiple tasks are passed, it throws a clear error message: "Task '[taskName]' contains spaces. Only a single Gradle task is allowed per executor invocation." This prevents the batch runner from misinterpreting the task name and provides immediate feedback to users about the correct usage. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes # (cherry picked from commit 94319c7)
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Current Behavior
The Gradle executor accepts a taskName option that should not contain multiple space-separated tasks. When multiple tasks are provided, the batch runner misinterprets the space-separated string as containing project names rather than treating it as a single task argument, leading to execution errors and confusion.
This only occurs if the taskName is manually overridden and should not occur when task names are generated by the project graph plugin.
Expected Behavior
The Gradle executor now validates that taskName contains only a single task without spaces. If multiple tasks are passed, it throws a clear error message: "Task '[taskName]' contains spaces. Only a single Gradle task is allowed per executor invocation." This prevents the batch runner from misinterpreting the task name and provides immediate feedback to users about the correct usage.
Related Issue(s)
Fixes #