Provide some standard format to write such information into a file and have some core infrastructure pick it up. This may be similar to, or perhaps included in the heartbeat page, but not only verbose in case of errors.
Thank you for your idea.
Could you please provide more data, so we will understand better your use case and the desired outcome? What kind of information is important and how it will help you?
- Dmitriy Mikhailov
Hi Dmitriy, in the first step this would be a) the git commit information and the b) "marketing version" of the deployment. Also c) the deployment time would be useful. When possible, also some Changelog could be generated. Everything points in the same direction: to be able to provide information to someone how is not able to access the server via ssh etc. to make sure e.g. bugs are filed correctly. Currently we included for example https://www.npmjs.com/package/node-git-info-json into our project. Georg
Hi!We generate a file during the CI process which gets filled by git commit hash, version tag, ci job id and triggering user for example. Every CI Pipeline should have such variables.The content of this file is shown in zed backend gui under maintenance included through a twig template.Should be easily implemented and every backend user with the proper rights should be able to view it.Best regardsMarc
You won't be notified about changes to this idea.