Feature #4248
Updated by Brett Smith over 9 years ago
qr1hi-8i9sb-h6ur26bp5gzd6am failed. is a run-command job that ran to completion. It uploaded all of its output to Keep. But Bryan knows that even after that, it tried to make an API request using a portable data hash+permission hint. That failed, and the whole job failed command produces output, and it's much easier to diagnose as a result. I haven't dug deeply, but my guess is that problem this all would've worked if he can see it. In this specific case, run-command recorded a manifest in the task output, and permission hint was gone. If that's right, we were able need to use figure out what tool or function output it, and then ask whether that tool needs to recreate be adjusted, or run-command edited to accommodate. Not assigning a Collection. But this required a lot of manual futzing. It would speed up pipeline development if this information were more readily accessible. This may require designing rules or conventions about how tasks record their output (which might be part of the larger reusable tasks discussion). category yet, pending that investigation.