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

fix(artifacts): Use client error return code for missing artifacts #2524

Merged
merged 1 commit into from
Nov 26, 2018
Merged

fix(artifacts): Use client error return code for missing artifacts #2524

merged 1 commit into from
Nov 26, 2018

Conversation

ezimanyi
Copy link
Contributor

When a pipeline is missing artifacts on startup, we currently throw an IllegalStateException, which eventually returns a 500 code to the client. As this is a problem with the request, and it should not be retried, let's be more clear by making it an IllegalArgumentException, which returns a 400 code.

When a pipeline is missing artifacts on startup, we currently throw
an IllegalStateException, which eventually returns a 500 code to the
client.  As this is a problem with the request, and it should not be
retried, let's be more clear by making it an IllegalArgumentException,
which returns a 400 code.
@dbyron0
Copy link
Contributor

dbyron0 commented Nov 26, 2018

Pretty sure this addresses spinnaker/spinnaker#3201. Thanks much!

@ezimanyi
Copy link
Contributor Author

@dbyron0 : Yes this (and spinnaker/echo#402) do indeed address that issue. I'll close the issue!

dreynaud pushed a commit to dreynaud/orca that referenced this pull request Dec 4, 2018
…pinnaker#2524)

When a pipeline is missing artifacts on startup, we currently throw
an IllegalStateException, which eventually returns a 500 code to the
client.  As this is a problem with the request, and it should not be
retried, let's be more clear by making it an IllegalArgumentException,
which returns a 400 code.
clanesf pushed a commit to clanesf/orca that referenced this pull request Dec 8, 2018
…pinnaker#2524)

When a pipeline is missing artifacts on startup, we currently throw
an IllegalStateException, which eventually returns a 500 code to the
client.  As this is a problem with the request, and it should not be
retried, let's be more clear by making it an IllegalArgumentException,
which returns a 400 code.
jervi added a commit to jervi/orca that referenced this pull request May 29, 2019
Same fix as spinnaker#2524, but for the case where multiple artifacts matches. Without this, Echo will try to trigger the pipeline five times and it will appear five times in the execution list.
ezimanyi pushed a commit that referenced this pull request May 29, 2019
…#2942)

Same fix as #2524, but for the case where multiple artifacts matches. Without this, Echo will try to trigger the pipeline five times and it will appear five times in the execution list.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants