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
Script results aren't saved if artifacts aren't found #1472
Comments
it is workflow definition issue. Code change doesn't make any impact. Try below changes To upload artifacts:
if you want
I can see the output
|
Yep. The issue is the fact the path for the output doesn't exist. However, it would be very beneficial to have the |
@searsaw we are actually changing the behavior of conditionally storing the script's outputs, depending on if the script output is actually used some place else. The reason for this is: #1359. Even if #1474 is merged, it would not solve your problem since with the new behavior, That said, if the script's output.result is referenced later in the workflow, then PR #1474 would help. |
Is this still a problem please? |
@alexec I think this is a nonissue at this point. |
Ok. Closing. |
Is this a BUG REPORT or FEATURE REQUEST?:
Bug.
What happened:
When running a step to install node dependencies, the install failed, which is fine. However, the stdout from that step telling me that the
package.json
wasn't present wasn't put into theoutputs.result
in the NodeStatus struct like I'd expect.What you expected to happen:
I expected
outputs.result
to have the logs from the container in it.How to reproduce it (as minimally and precisely as possible):
Run this and then look at the Node Status of the
install-deps
step. It has a message saying it can't save the output but there isn't any result showing the logsnpm install
outputted.Environment:
Other debugging information (if applicable):
I believe I know what the issue is and will be submitting a PR soon.
The text was updated successfully, but these errors were encountered: