rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1492909086
> Surely the version of Hugo provided by Jenkins is effectively pinned?
It indeed is pinned. But if INFRA (or another project) requests the version
to be updated then we might
rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1493320573
> > But it seems that only works for maven, jdk and gradle:
https://www.jenkins.io/doc/book/pipeline/syntax/#supported-tools.
>
> However https://www.jenkins.io/doc/book/managi
rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1493328882
@sebbASF does this look okay to you to be merged?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abo
rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1496356352
They are used once in the `${HUGO} version` and once in the actual `${HUGO}
--destination` call. Same for pagefind.
--
This is an automated message from the Apache Git Service.
To
rlenferink commented on PR #100:
URL: https://github.com/apache/comdev-site/pull/100#issuecomment-1497064040
> however the version calls were added for debug purposes and are not needed
Removed those statements and simplified the call to Hugo (per your
suggestions)
--
This is an au