Power Platform Build Tools automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.
MIT License
186
stars
38
forks
source link
All pipelines giving: The input does not contain any JSON tokens. #981
We are seeing this error message across extract, build and deployment pipelines, both classic and yaml when trying to deploy Power Platform Solutions and Function Apps
"Error: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. Path: $ | LineNumber: 0 | BytePositionInLine: 0."
Mostly the issue occurs when when have 2 agents running at the same time on self hosted machines, but not consistently so. This started happening on or around the 15th of July. Up to that point we have made no changes to our pipelines. Since this error we have updated our build agents to version 3.242.1 from 3.218.0 following guidance from Microsoft. We have checked the power platform tools version in our task groups and it is 2.*
Expected behaviour
Not to see this error
Screenshots
n/a
Desktop (please complete the following information):
Build servers are Windows Server 2016 Datacenter Version 1607
We are seeing this error message across extract, build and deployment pipelines, both classic and yaml when trying to deploy Power Platform Solutions and Function Apps
"Error: The input does not contain any JSON tokens. Expected the input to start with a valid JSON token, when isFinalBlock is true. Path: $ | LineNumber: 0 | BytePositionInLine: 0."
Mostly the issue occurs when when have 2 agents running at the same time on self hosted machines, but not consistently so. This started happening on or around the 15th of July. Up to that point we have made no changes to our pipelines. Since this error we have updated our build agents to version 3.242.1 from 3.218.0 following guidance from Microsoft. We have checked the power platform tools version in our task groups and it is 2.*
Expected behaviour Not to see this error
Screenshots n/a
Desktop (please complete the following information): Build servers are Windows Server 2016 Datacenter Version 1607