-
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
[REGRESSION]: PublishSymbolsV2 v2.246.1 task fails with "ScriptHalted" #20475
Comments
I am also hitting this issue with our build pipeline. |
Hi, Thank You in advance. |
Hi @ocitrev
|
Our TFVC projects are having this issue as well. To edit the YAML directly the classic pipeline must be migrated to a YAML pipeline as specified here: Unfortunately it seems that projects must first be migrated from TFVC to git in order to use the newer YAML pipelines. Here is a developer community thread I found on the subject: ------------------ Edit: We have found a temporary fix by simply changing the publish symbols task version from 2.* to 1.* |
Our TFVC through ADO pipelines are also failing this way. Started about 48 hours ago (last two daily builds, plus all manual runs). Working around it by marking the task "Warn if failed" and "Continue on error". |
We are experiencing the same error. Given our luck with having any of these errors with build tasks fixed in a timely manner (which is to say whoever "maintains" them clearly does not pay attention or care when they break lots of production builds) I do not assume it will be fixed anytime soon. Surprise me...please. |
@Deekshitha981 Can your openssl change be rolled back so the task works? ;-) |
Hi @Th3C0d3M0nk3y |
@carl-tanner Could you or your team please check the issue? |
More information: v2.246.1 appears to work if you are not indexing sources. My YAML pipelines for GitHub-based code run just fine without any errors or specifying a downgraded version. |
I was able to manually downgrade to 2.244.1 by copying the 2.244.1 files into the 2.246.1 folder on the build agent machine. |
Anyone able to find any other work arounds? I was unable to find a way to downgrade specifically to 2.244.1 outside of what @ocitrev suggested above. Downgrading to 1.* is causing our pipelines to have other issues, so that isn't a viable workaround for us. |
Disabling indexing sources avoids the issue for us. Not the ideal solution, but it does publish the symbol files that way. |
I'm having this problem as well. Currently can use the build pipeline output despite the warning, but would like to see the build succeed rather than finish with alerts. |
v2.246.3 fails with the same issue. |
Failed for me as well |
Same issue. Please fix and stop breaking things we depend upon to run our business. |
Sorry for the inconvenience. Task is reverted with version pointing to 2.246.3 -> 2.244.1 and 2.246.1 -> 2.244.1. Issue is fixed and it should rollout soon |
Confirming I can run builds now without issue. Thank you @viralpandya |
Thank you @viralpandya |
New issue checklist
Task name
PublishSymbolsV2
Breaking task version
2.246.1
Last working task version
2.244.1
Regression Description
The task simply fails with ScriptHalted. The log (see below) implies that it was unable to find Newtonsoft.Json.dll. No changes to our pipelines were made.
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 Server 2019, Windows Server 2022
Relevant log output
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
The text was updated successfully, but these errors were encountered: