QA (public) » openQA Project (public) » openQA Infrastructure (public)

szarate wrote:

[…] pointing to a .md file would work, that could keep the same structure as our current deployment schedule.

That wiki page was not updated for a year. How is it supposed to work differently now? And also: As long as we are talking about an osd-only solution I doubt the real need of QA engineers would be sufficiently adressed. How about an automatic email to the mailing list triggered by salt/deployment-script?

@okurz Email comes naturally after everything is done.

The idea of the link to a delta fits into an automated deploy, which chould generate the information and publish it, no human needed :).

In any case, the solution should be kind of agnostic or as agnostic as possible, so that it can be used with other deployments. Pretty much like the changelog feature that we have... (That nobody uses)

szarate wrote:

The idea of the link to a delta fits into an automated deploy, which chould generate the information and publish it, no human needed :).

Certainly. Take for example the automatic submit requests to openSUSE Factory that are created based on the openQA-in-openQA tests, e.g. https://build.opensuse.org/request/show/639153 which already provides a changelog. When we would ensure to update automatically to each new tested version then the changelog in the submit request would be equivalent to the changelog of what got deployed, problem solved :)