Oh, and if a system VM is touched, then you have to add in a new system VM
build and install into the CI setup prior to testing...
On Jul 1, 2017 6:41 PM, wrote:
Which is part of the reason the RM job is hard and time consuming.
- checking the PRs have the appropriate tests.
- updating the CI to
Which is part of the reason the RM job is hard and time consuming.
- checking the PRs have the appropriate tests.
- updating the CI to include the new tests.
- run and report CI for the PR (with very limited CI infra community wide).
- chase PR authors to get their PRs to a point where you are happ
Yes, we can totally reject PRs until we are happy with the associated
tests.
On Jul 1, 2017 5:48 PM, "Alex Hitchins" wrote:
> Out of interest, are there any guidelines/rules in place to reject PR's
> without unit tests?
>
>
>
>
> Alexander Hitchins
>
> E: a...@alexhitchi
Out of interest, are there any guidelines/rules in place to reject PR's without
unit tests?
Alexander Hitchins
E: a...@alexhitchins.com
W: alexhitchins.com
M: 07788 423 969
T: 01892 523 587
-Original Message-
From: Paul Angus [mailto:paul.an...@shapeblue.com]
Do all of these combinations need to be fully tested for each release?
What are the combinations that have been tested for the current release?
How many of these combinations are known to be running in production?
How many of these production organizations have test environments that
could be
