OK, that’s good, but what about the commit OIDs of all the other repos/branches
contributing to the website?
David Jencks
> On Nov 3, 2020, at 1:00 AM, Zoran Regvart wrote:
>
> Hi David,
>
> On Tue, Nov 3, 2020 at 6:19 AM David Jencks wrote:
>> ... it would be helpful to record the git commi
Hi Cameleers,
so this has been done on the latest build of the website and a fresh
clone of the website is now 569MB (178MB in .git), so about half of
the previous size.
zoran
On Mon, Nov 2, 2020 at 1:00 PM Zoran Regvart wrote:
>
> Hi Cameleers,
> when cloned the camel-website repository is 1.3G
Hi!
I just came across this coverage tool integration
https://coveralls.io/features and I immediately thought of this
thread. We would still have the problem of testing being a long job,
but I like the idea of having a notification per request saying if the
coverage is better or worse.
Cheers!
Ma
Dear Camelers,
As usual, we'd like to cut the next release of Camel Quarkus right after
Quarkus 1.10.0.Final which is planned for Wed., Nov. 18th.
If there is something, you'd like to get into the new release, please do
not hesitate to send a PR.
Thanks,
-- Peter
Hi David,
On Tue, Nov 3, 2020 at 6:19 AM David Jencks wrote:
> ... it would be helpful to record the git commit OIDs for each branch in the
> build each time the site is published.
I've fixed[1] the linkage between the `master` and the `asf-site`
branch, that should be correct now. So if you lo
