Pipeline requirements

[drBosse]

The test results must be archived by the integration job

The pipeline lacks visualization of any kind of metrics

• static analysis
• documentation check
• tsak scanner viz

[buep]

Changelog!

[JKrag]

This project is also a showcase and thus we probably want to invest in making the pipeline state-of-the-art and looking slick. It must also be publicly visible.

[buep]

Publishing changelog also to docs and the release binary :-)

[drBosse]

Should really have 2 pipelines, one for PiP one for PR

[buep]

I would like one pipeline, that reacts on the our normal work flow and one that builds newly opened pull requests (or changed ones) to tell us if they pass before we look at them.
Unless it is just a collaboration request... asking for second pair of eyes on code or ideas.

When we then accept the PR, it follows our ordinary flow (because we merge it to a ready branch maybe).

Imagine if you were a contributor, you would have our pipeline to play ball against... and all our nice environments, just by pushing to a PR...

[drBosse]

Makes perfect sense to reuse the PretestedPipeline for PR as well