Bug 1187510
| Summary: | kie-config-cli: add-deployment operation says successfull event though deployment failed. | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marek Baluch <mbaluch> |
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> |
| Status: | CLOSED WONTFIX | QA Contact: | Pavel Kralik <pkralik> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1.0 | CC: | kverlaen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-07 16:53:53 UTC | Type: | Enhancement |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
this is unfortunately current limitation of the kie-config-cli tool as it simply places information about deployment into system git over ssh push operation. So it does not have option to verify if the deployment actually was successful or not although operation of adding it to the system git repository was successful and this this info message - deployment has been successfully added and not deployed. It is planned to be enhanced when we rewrite the kie-config-cli to use REST api instead of using directly git repo. For now we can either close this as won't fix or transfer it as feature request for next release. Thoughts? closing as part of bugzilla cleanup, will be revisited when moving kie-config-cli to REST |
Description of problem: As per ${summary}. This happens in two cases: - When an existing project deployment fails - When a non existing project deployment is attempted. Steps to Reproduce: 1. Try to deploy groupId = non, artifactId = existent, version = -1 Actual results: Result: Deployment non:existent:-1 has been successfully added Expected results: Result: Deployment non:existent:-1 has failed with message: XYZ Additional info: Input values like valid Runtime Strategy value are not validated.