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

Improve messages stored in error variables #1872

Closed
MJRichardson opened this issue Aug 10, 2015 · 9 comments
Closed

Improve messages stored in error variables #1872

MJRichardson opened this issue Aug 10, 2015 · 9 comments
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Milestone

Comments

@MJRichardson
Copy link

MJRichardson commented Aug 10, 2015

The values stored in Octopus.Deployment.Error and Octopus.Deployment.ErrorDetail (and their Step scoped versions) could be more useful.

Currently 'One or more child activities failed.' is being stored in Octopus.Deployment.Error, and Octopus.Deployment.ErrorDetail contains something along the lines of

Octopus.Shared.Tasks.ActivityFailedException: One or more child activities failed.
   at Octopus.Shared.Tasks.ParallelWorkOrder`1.AssertAllCompletedTasksThusFarAreSuccessful() in y:\work\refs\heads\master\source\Octopus.Shared\Tasks\ParallelWorkOrder.cs:line 78
   at Octopus.Shared.Tasks.ParallelWorkOrder`1.Execute() in y:\work\refs\heads\master\source\Octopus.Shared\Tasks\ParallelWorkOrder.cs:line 33
   at Octopus.Shared.Tasks.OctoParallel.ForEach[T](IEnumerable`1 workItems, Nullable`1 maxParallelism, Action`1 executeCallback, CancellationToken cancellation) in y:\work\refs\heads\master\source\Octopus.Shared\Tasks\OctoParallel.cs:line 20
   at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.DistributeStepAcrossMachines(PlannedStep step) in y:\work\refs\heads\master\source\Octopus.Server\Orchestration\Deploy\DeploymentTaskController.cs:line 174
   at Octopus.Server.Orchestration.Deploy.DeploymentTaskController.DispatchStep(PlannedStep step) in y:\work\refs\heads\master\source\Octopus.Server\Orchestration\Deploy\DeploymentTaskController.cs:line 76
@MJRichardson MJRichardson added the kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time label Aug 10, 2015
@MJRichardson
Copy link
Author

@Irrational86
Copy link

@DamianMac Does this mean that this won't be done?

@robpearson
Copy link

robpearson commented Apr 26, 2016

Found another instance of this issue. Re-opening the issue.

Source: http://help.octopusdeploy.com/discussions/problems/45082

@robpearson robpearson reopened this Apr 26, 2016
@vanessalove
Copy link
Contributor

thought this was done here: #2216
but customer is on 3.3+

@robpearson
Copy link

@vanessalove This is a slightly different bug/error. This occurs when the steps are executed in parallel and it's a diff code path.

@markryd markryd self-assigned this Jun 26, 2016
@markryd markryd added in progress and removed ready labels Jun 26, 2016
@markryd
Copy link

markryd commented Jun 27, 2016

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.

@markryd markryd closed this as completed Jun 28, 2016
@octoreleasebot octoreleasebot added this to the 3.3.20 milestone Jun 28, 2016
@octoreleasebot
Copy link

Release Note: Octopus.Deployment.Error now contains better information if a parallel step fails

@JesseNaranjo
Copy link

@markryd Thanks so much for implementing this!

@lock
Copy link

lock bot commented Nov 25, 2018

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.

@lock lock bot unassigned markryd Nov 25, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Projects
None yet
Development

No branches or pull requests

8 participants