We use Gitlab to run pipelines and deploy applications automatically through the xl client (command "xl apply") into different environments.
If the deployment fails (as example due to missing / wrong substitutes or configuration problems in the deploy-environment) the client does not really speak. The pipeline fails and the response in Gitlab is:
Error while processing YAML document at line 1 of XL YAML file /builds
Unexpected response:
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1
After that the user must manually go to the deploy GUI, check if the package is available under applications, simulate the deployment step to see if there are (as example) missing substitutes in the package ("Placeholder abc doesn`t have a value") or dictionary. In the GUI the error problem is declared better and "on point" while simulating a deployment.
It would be easier and faster if the xl client could catch up this error messages from deploy and pipe them through back to Gitlab so the user knows what is wrong, can fix it and rerun the pipeline without changing the tools and test manually.
by: Christian H. | 6 months ago | API & CLI tools
Comments
Thank you for the suggestion. We agree on its necessity. We will investigate in July to determine if additional details can be exposed via XL CLI and will update this thread accordingly.
This change is now available in version 24.3. We welcome any additional comments or suggestions you may have. For more details, please refer to the release notes:
https://docs.digital.ai/bundle/devops-deploy-version-v.24.3/page/deploy/release-notes/releasemanual_deploy_v.24.3.html#enhanced-xl-cli-error-messages