Hi,
On Wed, Aug 7, 2019 at 1:33 PM Zoran Regvart wrote:
>
> ...for the Camel website we opted using docker containers with the
> required tools instead of relying on the tools provided on the build
> nodes
Did you get this to run on an ASF build service, or do people have to
run the build lo
Have you had an opportunity to make progress on this, to share with us?
Anybody else with news?
Thanks!
-g
InfraAdmin, ASF
On Tue, Aug 13, 2019 at 3:59 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> I've made a simple PoC for the Apache Maven Dependency Plugin on a
> separate branch.
>
> I will try
I have implemented the ability to generate the website and javadoc for
Calcite using Github Actions. See:
https://github.com/apache/calcite/tree/test-site/.github/workflows
The missing piece is that we need the token to publish to our
calcite-site repository to be added as a secret in Github A
Hi Francis,
Is the token needed to push from calcite to calcite-site? Is that an oauth
token or something? And are you able to use the repository settings to add
secrets, but you don't have the right token? Or you cannot add secrets at
all? (I can't tell since I have superpowers)
I've added GSTEI
How to avoid leaking secrets: only way to do that is via pre-verified code
that executes something with that secret. Otherwise, there’s literally
infinite ways to leak it being a Turing machine and all. This applies to
all CICD tools.
On Tue, Aug 27, 2019 at 20:32, Greg Stein wrote:
> Hi Francis
Yeah. FIgured as much, hoped that I was missing something :)
(note: we have the same issue with buildbot and jenkins: we simply trust
the communities to not exfil that data)
On Tue, Aug 27, 2019 at 9:16 PM Matt Sicker wrote:
> How to avoid leaking secrets: only way to do that is via pre-verifie
