Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsuccessful deployments show up as successful when deploying from modeler #838

Closed
benhoffmann opened this issue Jun 22, 2018 · 3 comments
Closed
Assignees
Labels
bug Something isn't working deploy
Milestone

Comments

@benhoffmann
Copy link

If I deploy a model directly from the modeler, it says "Deployment was done successfully" even if this was not the case. My engine complained with a BPMN parse error and did not deploy the diagram, but the modeler did not catch that problem.

v 1.16.0

@nikku nikku added bug Something isn't working deploy backlog Queued in backlog labels Jun 27, 2018
@fractallian
Copy link

Would be extremely helpful to surface model parsing errors in the modeler. I see errors using the API but modeler just says deployment succeeds for the same file.

@Alexander-Kiselyov
Copy link

Alexander-Kiselyov commented Sep 23, 2018

Create Deployment endpoint does respond with an error - HTTP 500 - when I try to deploy a definition with a process-level Event Subprocess triggered by a Compensation Start Event (not supported according to the doc):

> POST /engine-rest/deployment/create HTTP/1.1
> Host: localhost:8081
> User-Agent: curl/7.55.1
> Accept: */*
> Content-Length: 12747
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=------------------------75a62bae9b8408af
>
< HTTP/1.1 100
< HTTP/1.1 500
< Content-Type: application/json
< Transfer-Encoding: chunked
< Date: Sun, 23 Sep 2018 20:24:26 GMT
< Connection: close
<
{"type":"ProcessEngineException","message":"ENGINE-09005 Could not parse BPMN process. Errors: \n* event subprocess with compensation start event is only supported for embedded subprocess (since throwing compensation through a call activity-induced process hierarchy is not supported) | testprocess.bpmn | line 30 | column 48"}* Closing connection 0

I'm not a JS expert, but as I understand, deployment logic is located in app/lib/createDeployer.js, and, as far as I see in fetch() docs, 500 won't lead to throwing an error.

@nikku nikku added ready Ready to be worked on and removed backlog Queued in backlog labels Nov 23, 2018
@nikku nikku added this to the M26 milestone Nov 23, 2018
barmac added a commit that referenced this issue Nov 27, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
Closes #846
barmac added a commit that referenced this issue Nov 27, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
barmac added a commit that referenced this issue Nov 28, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
@ghost ghost assigned barmac Nov 29, 2018
@ghost ghost added needs review Review pending and removed ready Ready to be worked on labels Nov 29, 2018
barmac added a commit that referenced this issue Dec 3, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
barmac added a commit that referenced this issue Dec 3, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
barmac added a commit that referenced this issue Dec 3, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
barmac added a commit that referenced this issue Dec 4, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
barmac added a commit that referenced this issue Dec 4, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
barmac added a commit that referenced this issue Dec 5, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
nikku pushed a commit that referenced this issue Dec 10, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
merge-me bot pushed a commit that referenced this issue Dec 10, 2018
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
@nikku
Copy link
Member

nikku commented Dec 10, 2018

Closed via #1041.

@nikku nikku closed this as completed Dec 10, 2018
@ghost ghost removed the needs review Review pending label Dec 10, 2018
barmac added a commit that referenced this issue Jan 17, 2019
* use endpoint url provided by client
* display user-friendly error messages
* do not throw error for response other than JSON

Closes #838
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working deploy
Projects
None yet
Development

No branches or pull requests

5 participants