Please excuse me, if I overlooked existing infrastructure. I just started getting more familiar with the code.

CI/CD helps to not only find quality issues early, but also provides a less error-prone process for tasks, that are automated by this. @peerchemist mentioned that it would be nice to have regular builds so more people can test new versions in a chat.
He also pointed me to https://github.com/faddat/peercoin where there is already first step in that direction.

I would like to track the goals and progress in this issue and also give others a chance to see, where more things could be done. So people do not do things which are already solved.

We should also avoid trying to do everything at once. Especially with the release automation… it is important to keep security aspects in mind (proper checking of signatures, clear distinction between CI-signed and developer-signed artifacts etc.)

Maybe @faddat could help me figure out where things are at right now and add info to this issue.

Personally I have the following scopes for CI/CD with all my projects:

1. Automated code-tests (Unit-tests) of PRs
2. Automated Integratin-Tests (platforms, architectures, etc.), also scheduled/done regularly
3. Tracking of test-coverage and lack thereof in critical areas
4. Automated test-builds and updated documentation pages, if applicable
5. Static code analysis and reports
6. Automated nightly builds for users to test.

The lowest hanging fruits are 1., 3. and maybe 4.

Happy to hear more input/thoughts on this!