It is possible to configure the leak period to a specific date, which is nicely described in the appropriate section of the interface, but this description does not make clear whether the leak period is inclusive or exclusive of that date. It should.
For instance, if I set the leak to 2018-01-01, is code committed on New Years day in the leak period?
Testing with leak period set to 2018-01-01 and 3 analyses dated:
- 2017-12-31 // first analysis
- 2018-01-01 // new issue introduced here not in leak
- 2018-01-02 // new issue introduced here in leak
Testing with leak period set to 2018-08-07 and analyzing twice on that day
- 1st analysis - baseline; issues not in leak period
- 2nd analysis - in leak period.
The settings interface says this:
When specifying a number of days or a date, the snapshot selected for comparison is the first one available inside the corresponding time range.
which is clear enough once you know how it works. :-/
Let's expand it to:
When specifying a number of days or a date, the snapshot selected as the baseline for comparison is the first one available inside the corresponding time range. Specifically, the first analysis in the range is considered to be before the leak period(/new code period).
For the second test, the leak period header on the project homepage says:
Leak Period: since 2018-08-07
Ideally we'll make the timestamp of the relevant snapshot available and say something like
Leak Period: after 2018-08-07 13:26
(or whatever the time localization produces).