This just introduces some basic warning capturing functionality.
It doesn't capture warnings from anything that a user may do during a build, but anything that we decide to capture will easily be able to utilise the functionality.
It would be cool to be able to capture things from a docker image build process, or from a pre/post rollout task, but this would require parsing the logs from these processes, which we currently do not do (but could maybe do in the future?)
This does not require the UI changes to be merged, the UI changes just make the warnings actually show up, otherwise the warning features are ignored.
This just introduces some basic warning capturing functionality.
It doesn't capture warnings from anything that a user may do during a build, but anything that we decide to capture will easily be able to utilise the functionality.
It would be cool to be able to capture things from a docker image build process, or from a pre/post rollout task, but this would require parsing the logs from these processes, which we currently do not do (but could maybe do in the future?)
This does not require the UI changes to be merged, the UI changes just make the warnings actually show up, otherwise the warning features are ignored.