Ideas

Make deployment information accessible at runtime

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.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 18 2018
  • In review
How we can make you more productive?

Provide some infrastructure to include such information to not force every project to (discuss, plan and) build it on project level

Company Winterhalter-Fenner AG
  • Attach files
  • Admin
    Dmitriy Mikhailov commented
    25 Sep 14:24

    Hi Georg,

    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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    25 Sep 14:57

    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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    05 Dec 21:06

    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 regards
    Marc