-
Notifications
You must be signed in to change notification settings - Fork 20
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Improve messages stored in error variables #1872
Comments
Please update http://help.octopusdeploy.com/discussions/problems/37083-error-and-errordetail-do-not-show-the-correct-information when implemented. |
@DamianMac Does this mean that this won't be done? |
Found another instance of this issue. Re-opening the issue. Source: http://help.octopusdeploy.com/discussions/problems/45082 |
thought this was done here: #2216 |
@vanessalove This is a slightly different bug/error. This occurs when the steps are executed in parallel and it's a diff code path. |
I'll fix things so the error contains the Step name and Machine name when a parallel task fails rather than just "A child task failed", but we are still going to end up with "The remote script failed with exit code 1" in the case of failing powershell steps since that is the error octopus sees. We never see the actual powershell error. We could potentially suck out the StdErr output and if we wanted. |
Release Note: |
@markryd Thanks so much for implementing this! |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately. |
The values stored in
Octopus.Deployment.Error
andOctopus.Deployment.ErrorDetail
(and their Step scoped versions) could be more useful.Currently
'One or more child activities failed.'
is being stored inOctopus.Deployment.Error
, andOctopus.Deployment.ErrorDetail
contains something along the lines ofThe text was updated successfully, but these errors were encountered: