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): Fix NPE on empty artifact #373

Merged
merged 1 commit into from
May 17, 2019
Merged

fix(artifacts): Fix NPE on empty artifact #373

merged 1 commit into from
May 17, 2019

Conversation

ezimanyi
Copy link
Contributor

Fixes spinnaker/spinnaker#4387

If an artifact is empty, we throw an NPE when downloading it rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but in some cases (ex: a values.yaml file for a Helm bake) it's reasonable to have no content.

If an artifact is empty, we throw an NPE when downloading it
rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but
in some cases (ex: a values.yaml file for a Helm bake) it's reasonable
to have no content.
Copy link
Contributor

@ethanfrogers ethanfrogers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@ezimanyi ezimanyi merged commit a8d60cb into spinnaker:master May 17, 2019
@ezimanyi
Copy link
Contributor Author

@spinnakerbot cherry-pick 1.14

@ezimanyi ezimanyi deleted the fix-empty-artifact branch May 17, 2019 20:20
spinnakerbot pushed a commit that referenced this pull request May 17, 2019
If an artifact is empty, we throw an NPE when downloading it
rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but
in some cases (ex: a values.yaml file for a Helm bake) it's reasonable
to have no content.
@spinnakerbot
Copy link
Contributor

Cherry pick successful: #374

ezimanyi pushed a commit that referenced this pull request May 17, 2019
If an artifact is empty, we throw an NPE when downloading it
rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but
in some cases (ex: a values.yaml file for a Helm bake) it's reasonable
to have no content.
opsmxdemo pushed a commit to OpsMx/rosco that referenced this pull request Sep 15, 2020
If an artifact is empty, we throw an NPE when downloading it
rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but
in some cases (ex: a values.yaml file for a Helm bake) it's reasonable
to have no content.
opsmxdemo pushed a commit to OpsMx/rosco that referenced this pull request Sep 16, 2020
If an artifact is empty, we throw an NPE when downloading it
rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but
in some cases (ex: a values.yaml file for a Helm bake) it's reasonable
to have no content.
sitay93 pushed a commit to spotinst/spinnaker-rosco that referenced this pull request Jun 27, 2023
)

If an artifact is empty, we throw an NPE when downloading it
rather than just pass an empty artifact along to the caller.

In general it's not overly useful to have an empty artifact, but
in some cases (ex: a values.yaml file for a Helm bake) it's reasonable
to have no content.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants