Hi All,
since yesterday around 11:00AM UTC, we are facing issues with Forge deploy. The error message is not really helpful:
Upload URL is valid
Found manifest file
Manifest is a valid YAML
Manifest validation failed
Validation errors: {
"validationResult": {
"tid": "5e1b98eac5d2e550",
"code": 400,
"type": "UpsertEnvironmentRequestInvalidError",
"message": "Upsert Environment Request body is invalid. Details "
}
}
Error: Deployment failed
Error: Deployment failed
at ArtifactDeployer.handleErrorEvent (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\deploy\deployer\deployer.js:151:15)
at ArtifactDeployer.pollAndCheckEvents (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\deploy\deployer\deployer.js:61:18)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async ArtifactDeployer.monitorDeployment (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\deploy\deployer\deployer.js:72:28)
at async ArtifactDeployer.deploy (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\deploy\deployer\deployer.js:36:9)
at async PackageUploadDeployCommand.execute (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\deploy\package-upload-deploy.js:14:9)
at async CommandLineUI.displayProgress (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\node_modules\@forge\cli-shared\out\ui\command-line-ui.js:44:28)
at async DeployView.reportDeploymentProgress (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\command-line\view\deploy-view.js:50:24)
at async DeployController.run (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\command-line\controller\deploy-controller.js:122:27)
at async Command.actionProcessor (C:\Users\gabor\AppData\Roaming\npm\node_modules\@forge\cli\out\command-line\command.js:76:32)
This affects our whole team. We made no changes to our manifest.yml file. I was able to deploy our app beforehand with the exact same manifest.yml that failed validation an hour later. I updated Forge CLI to the latest version but it did not help.
I’ve searched community topics for the error message above and found that others faced similar problems before, but the fixes to those problems are not relevant in our case.
My questions:
- Did anything change in Forge’s manifest validation process? If yes, is there a post we can take a look at to see what changed? Maybe it has been announced in advance and I missed it.
- Can you provide more meaningful error messages in general? “Manifest validation failed” followed by a cryptic validation result JSON is not helpful. In my team we all faced the same problem and wasted quite some time individually before realizing this is a generic problem and not some awkward individual issue.
@Atlassian Staff I can send our manifest.yml in PM if it helps.
Thanks,
Gabor
