You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed today that, when trying to add an additional step to the pipeline to notify Slack, I received the following error:
2024-12-13 16:51:28 WARN There were some issues with the pipeline input - pipeline upload will proceed, but might not succeed:
while unmarshaling the value for key "steps" into struct field "Steps"
↳ while unmarshaling step 1 of 1
↳ fell back using unknown type of step due to an unmarshaling error
↳ unmarshalling CommandStep: unmarshaling item at index 0 of 2: incompatible types: cannot unmarshal *ordered.Map[string,interface {}] into *string command=pipeline upload
This is given the following:
steps:
- label: "Something to write here"command:
- echo "Some context for the error message, blah: See https://github.com/...."
- exit 1agents:
image: busybox:latestnotify:
- slack:
channels:
- "#some-alerts-channel"
I noticed that when making the following change:
steps:
- label: "Something to write here"
command:
- - echo "Some context for the error message, blah: See https://github.com/...."+ - echo "Some context for the error message, blah. See https://github.com/...."
- exit 1
agents:
image: busybox:latest
notify:
- slack:
channels:
- "#some-alerts-channel"
Then the upload started working as expected.
It looks like there may be some additional YAML parsing/marshalling occurring, that doesn't seem to handle the : in the string.
The text was updated successfully, but these errors were encountered:
I noticed today that, when trying to add an additional step to the pipeline to notify Slack, I received the following error:
This is given the following:
I noticed that when making the following change:
Then the upload started working as expected.
It looks like there may be some additional YAML parsing/marshalling occurring, that doesn't seem to handle the
:
in the string.The text was updated successfully, but these errors were encountered: