We have automated deployments that run 24x7 during development.
Today, we had an unexpected server shutdown, and when the server came back up, the OD tentacle service did not start. Subsequently, several automatic deployments were queued up for over two hours – the first one was silently waiting for failure guidance.
Everyone was emailing me asking why their code has not yet been deployed! I finally had to login to the OD web to see what was going on.
OD developers, kindly make it a priority to send an email when guidance is needed.
NOTE: I do know about the suggestion on uservoice, but was unable to add my vote (out of votes???)
Thanks for getting in touch and providing feedback. I’ve circulated your feedback around our team as food for thought as we do enhancements and updates. That said, we don’t have anything planned for this at the moment. I would have suggested visiting our user voice page but you’re already aware of it.
In the meantime, I have a few suggestions to help mitigate the problem you described.
- It sounds like developers/teams don’t have access to the Octopus web portal. If they had access (i.e. read-only) they could find and potentially fix these issues themselves.
- Add infrastructure monitoring to alter you to when certain services aren’t running on servers. Monitoring tools like Microsoft’s SCOM or IBM’s tivoli are two big examples but numerous other free/cheap tools can be found via google.
Hope this helps!
Rob - Thanks for your note.
Regarding your suggestions:
It sounds like developers/teams don’t have access to the Octopus web portal.
They don’t have access to Octopus, by design. We have a release manager (currently myself) who is responsible for builds and deploys.
Add infrastructure monitoring to alter you to when certain services aren’t running on servers.
Interesting, but does not speak to the core of my issue, which is that when “failure guidance” is needed, someone must be physically looking at the web portal in order to be aware.
Put simply, it’s essential that there be other options (email, sms) for notifying the release manager in cases where failure guidance is required.
I hope to keep this simple but essential enhancement on your team’s radar.
This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.