Jenkins plug-in version currently uses xml to call run-deploymentplan REST API.
The best practice in REST API call is to use JSON format so the Kenkins plug-in should use JSON format instead.
I agree with Marc currently manifest file is an xml file and the same is passed via jenkins to Release Automation.
We should be having a way to pass release manifest file as a JSON file or system should translate it to same.
To recap, JSON should be a possible format for all contents:
- it should be possible to provide "Package Content" format in JSON
- it should be possible to provide "Release Manifest Content" in JSON
When "apply" or "Save", there should be an automatic syntax parsing of the manual content provided based on the selected format (JSON or XML).
In addition, "Generate Artifact package" and "Generate Release Manifest" options should generate JSON-format content.
Retrieving data ...