This will be my fallback solution if I can't get the job to trigger on a
tag push or a push to the site branch correctly.
The reason I wanted to build the javadocs only when a final release's
tag is pushed is because the javadocs takes around 20 minutes to build
on the node, whereas the site takes between 5 to 6 minutes. I think
needlessly building the javadocs every time the site is pushed is not as
efficient as I'd like the job to be.
On 4/07/2019 9:57 pm, Vladimir Sitnikov wrote:
Francis>- For Javadocs (Calcite and Avatica) trigger and build when a final
version is tagged.
I think javadocs could be built on each push to site branch.
Vladimir
