If pipelines are enabled, the "deploy history" should list pipeline objects, not DNDeployments

[ss23]

The prod list only shows successful releases when pipeline is enabled. Which means failed releases just disappear, and I can't see any way to view logs on WHY it failed after the fact. The emails being sent out on failure are similarly unhelpful (no reason for failure or link to logs).

Sam would suggest that, where pipelines are in use, we don't list the DNDeployment records—it's unnecessary and confusing. Perhaps the results of the relevant DNDeployment can be listed when you open the details of a single pipeline?

After fixing this, it would be worth looking at the comment history of #101 to confirm, as Sam assumes that this fix will have also addressed that.

cc @chillu

[tractorcow]

What's needed is a proper list of pipelines and their respective states, similar to the previous deployment history.

[sminnee]

I would suggest that, where pipelines are in use, we don't list the DNDeployment records—it's unnecessary and confusing. Perhaps the results of the relevant DNDeployment can be listed when you open the details of a single pipeline?

[tractorcow]

That's similar to what I am thinking Sam. :)
On 12 Nov 2014 16:16, "Sam Minnée" [email protected] wrote:

I would suggest that, where pipelines are in use, we don't list the
DNDeployment records—it's unnecessary and confusing. Perhaps the results of
the relevant DNDeployment can be listed when you open the details of a
single pipeline?

—
Reply to this email directly or view it on GitHub
#100 (comment)
.

[chillu]

My deploynaut pet peeve of the day: The lack of pipeline step visibility also means that you can't see WHEN a deployment actually went live (might be hours after it was requested), and WHO approved it.