-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: Java Tool Installer task failed after release 0.230.2 #19244
Comments
Hey, Please update your agents on agent pool. it works for me Thanks |
It works thank you. |
Same, what minimum version of Azure Pipeline Agent is required ? Or is this a bug that should be fixed on task ? |
Updating to on-prem Agent 3.227.2 works... |
For anyone else struggling with this problem, I updated the Self-Hosted Windows agent that I had problems with, from version 2.142.3 to version 3.227.2. The update did not take long (less than a minute), but I guess it depends on the agent. The agent might go offline for a short time, and going back online with the updated version. I do not think there is a minimum version of the agent required. |
Still getting this issue on Hosted-Agent 3.227.2 Using versions: |
We rolled-back to version 0.229.0 of the task, and we're using the Microsoft hosted window's-latest image. Worked fine for us. The caveat is that, the minor version of the task can only be specified if that specific version has been used in your Azure DevOps org before. See - https://github.com/MicrosoftDocs/azure-devops-docs/issues/8351 |
This issue should be fixed by this PR #19391 |
Closing this as the problem is fixed. Feel free to reopen if you still have the issue. |
Task name
Java Tool Installer
Task version
0.230.2
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows_NT
Task log
Relevant log output
Aditional info
No response
The text was updated successfully, but these errors were encountered: