top posting, yaay!
I have a new server sort of set up now. I'll have infra redirect to that
one instead, and it'll rebuild most of the database during the night
(and the next night, and...).
there's a new option, a path filter in the repos tab, which filters
commits, line changes, trends, top contributors etc by paths affected,
so you can enter either 'jbake' to get everything touching jbake, or
'!jbake' to get everything that doesn't touch those files.
The CNAME should switch over some time today :)
With regards,
Daniel.
PS: We're also switching to elasticsearch 6 with this move, which is
going to be great, as that allows us to test on a modern ES, instead of
the old 5.x installation we're currently running on.
On 09/12/2018 12:24 PM, Daniel Gruno wrote:
On 09/12/2018 12:22 PM, Robert Munteanu wrote:
If you look at the sling-site repository at [1] we have the actual
documentation under src/main/jbake, with
- content being markdown files
- templates being ... well ... templates
- and assets being static files
Some of those static files are generated (javadoc, Maven plugin sites)
and should not be recorded by Kiddle. Those are the ones that are
problematic, especially since we have a large number of javadocs
committed.
$ find src/main/jbake/assets/apidocs -type f | wc -l
7127
Those are the ones we'd like excluded, if at all possible.
Thanks,
Robert
[1]: https://github.com/apache/sling-site/tree/master/src/main/jbake
I've added a change to the scanners, so they will put a list of files
changes into each commit object we record. This is likely going to
require a complete re-scan of all things sling...which in theory is
fine, as I _was_ planning on moving the demo server to a new box anyway.
I'll let y'all know more when I have that worked out in my mind :)
After the move and re-scan, it should be possible to exclude by file paths.
