Display last migrated build and date besides Subdeployment name

OttoDeploy
,
1

We have deployments with a lot of subdeployments. Sometimes we need to deploy 1 or 2 subdeployments ahead of our schedule.
When we deploy the rest of the subdeployments we have no idea what subdeployment we already did.
It would be very helpful to see the last successfully deployed build as well as the time of the deployment besides the subdeployment.

Thanks!

2

Hey Tobias,

Thanks for the request! I’m hesitant to add features that track the history of deployment from within OttoDeploy as OttoDeploy doesn’t really know the whole picture of what is going on on the server since other copies of OttoDeploy and the Ottomatic Console can also kick off deployments to servers. The only true source of truth about when something was deployed is the deployments table in OttoFMS, and adding a history that is internal to OttoDeploy could possibly provide information that is incorrect.

That being said, I do appreciate that going from OttoDeploy to the OttoFMS console for each of the servers would be super annoying just to see when a sub-deployment was last run. We’ve worked on a similar history structure in the past, I’ll add this idea to it and see if it meshes well.

Thank you again for the suggestion!

-Kyle

3

Hi Kyle,

thanks for the reply. I do understand that one could start deployments from different files/angles but is that really a common problem. I think if you set up deployments for solutions you update regularly you would use a single file to control what gets deployed. Since you also see the last build you selected for the whole deployment and gain some information from that as well and another file could have already selected a different build it is all rather vague.
So I think the phrase “last deployment: Build ID, date” would be rather clear that it relates to this deployment.
Thanks for considering, Tobias

EDIT: for clarity

1 Like