HasWarningsOrErrors as an Octopus variable

[Chris_Camburn]

The Tasks API has a property “HasWarningsOrErrors” attached to it, but unfortunately there is currently no way to access this during a deployment (at least as far as I can see). I was hoping to use something similar to one of the following:

$OctopusParameters[“Octopus.Deployment.HasWarningsOrErrors”]
$OctopusParameters[“Octopus.Task.HasWarningsOrErrors”]
$OctopusParameters[“HasWarningsOrErrors”]

Can this be made available as a variable during deployments? Or is there a better way to check if the current deployment has warnings?

[henrik (Henrik Andersson)]

Hi Chris,

Thanks for getting in touch.

I’m assuming you want to get access to the HasWarningsOrErrors within the currently running deployment? Currently, if we get a warning during the deployment we don’t set any variable but if an error is encountered we set the Octopus.Action[_StepName_].Status.Error and Octopus.Action[_StepName_].Status.ErrorDetail variables so you could use those within a deployment.

Outside of the deployment you can retrieve the ServerTask during the running of the deployment and check the HasWarningsOrErrors property as it will be updated as soon as we hit a warning or error.

Worst case, you could retrieve the task details (api/tasks/{id}/details) and loop through all the LogElements of each ActivityLog entry on the task and see if any of their ActivityLogEntryCategory property are Warning|Error|Fatal.

Not sure if any of this will help you, but that’s all we have currently

Thank you and kind regards,
Henrik

[Chris_Camburn]

Hi Henrik,

The intended use is to customize both email and slack notifications. We have a number of scenarios where a deployment to certain environments is allowed but frowned upon for (such as deploying to Staging while using pre-release dependencies). We have to allow it for certain business needs, but we want to warn people that it cannot go to production. The goal was to check a certain variable for truthy status and then alter our notifications accordingly.

The following tickets both explicitly mention warnings, and one of them got a github issue a while back, but warnings were left out of Status so it didn’t cause a breaking change when checking Status == Success.

Gather warnings and errors during a deployment

Hi Boyan, Thanks for getting in touch! In Octopus we have a variable that is populated with the details of an error when it happens, however as a new error happens we override that variable with the new error. Outside of Octopus we don’t record errors or warnings apart from in the logs. How often are you encountering multiple errors in your deployments? If we had a bit more information on what you are looking to achieve then I may be able to give you a more helpful answer. Looking forward t…

A way to use the warning build status in steps?

So we want to send emails on status, currently we have some situations where we want to throw a warning in the build but not fail the build. Currently the email support only supports always, failed, and success. Ideally we would like to be able to report that the build had a warning in the email so that someone knows they should check on the logs. Are their any plans to either have a warning selector step condition or at least include the current status in an environmental variable?

Is it possible to include the same task.HasWarningsOrErrors as a variable? I know I can add code to query the API and find the status, but it seems that’s something that should be readily available.