Francis Chuang created CALCITE-6359:
---
Summary: Update GitHub Actions workflows to use docker compose v2
Key: CALCITE-6359
URL: https://issues.apache.org/jira/browse/CALCITE-6359
Project: Calcite
Francis Chuang created CALCITE-5235:
---
Summary: Run Github Actions tests using docker and upgrade Go
Key: CALCITE-5235
URL: https://issues.apache.org/jira/browse/CALCITE-5235
Project: Calcite
Francis Chuang created CALCITE-5059:
---
Summary: Update Github Actions to latest versions
Key: CALCITE-5059
URL: https://issues.apache.org/jira/browse/CALCITE-5059
Project: Calcite
Issue
Vladimir Sitnikov created CALCITE-4829:
--
Summary: Bump Gradle to 7.2 and test with Java 17 at GitHub Actions
Key: CALCITE-4829
URL: https://issues.apache.org/jira/browse/CALCITE-4829
Project
The actions have been approved, so GitHub CI is back on track :)
On top of that, I added potiuk/cancel-workflow-runs so it cancels workflows
if the branch or PR is updated multiple times.
Hopefully, it would reduce CI wait times.
Please share if you happen to love or hate it.
Vladimir
I have no evidence for this whatsoever, but I have a hunch that GitHub
actions could be exploited by bitcoin miners. I would be concerned
that someone could create a PR and burn several cents of Apache's (or
GitHub's) operational budget.
On Fri, Jan 8, 2021 at 9:53 AM Michael Mior wrote:
>
ted something like
> https://julienrenaux.fr/2019/12/20/github-actions-security-risk/#the-problem
> as a security issue to the ASF, and it triggered the wave :-(
>
> I guess they mentioned that tag-based and branch-based action
> references like AdoptOpenJDK/install-jdk@v1
> coul
Has there been a clear statement as to why the restrictions are in
place? Given that the workaround is so trivial, it seems like the
restriction is rather pointless.
--
Michael Mior
mm...@apache.org
Le jeu. 7 janv. 2021 à 11:53, Vladimir Sitnikov
a écrit :
>
> I've found a workaround that
I've found a workaround that unlocks arbitrary action.
See PR https://github.com/apache/calcite/pull/2318
The idea is to clone the action via git clone, and then use the "local"
folder as the action source.
As of now, we need only burrunan/gradle-cache-action
and AdoptOpenJDK/install-jdk,
so my
Francis> gradle/wrapper-validation-action@v1
It looks like wrapper-validation-action is already allowed for use.
Francis>burrunan/gradle-cache-action
I've filed https://issues.apache.org/jira/browse/INFRA-21275 to allow that
action.
Francis>- Avoid using third party actions, possibly replace
/12/2020 6:14 pm, Julian Hyde wrote:
As of yesterday, GitHub actions are disabled for any non-Apache repository. I
think this means that GitHub actions will not fire for PRs (which are typically
in the contributor’s repository).
See https://issues.apache.org/jira/browse/INFRA-21234
<ht
As of yesterday, GitHub actions are disabled for any non-Apache repository. I
think this means that GitHub actions will not fire for PRs (which are typically
in the contributor’s repository).
See https://issues.apache.org/jira/browse/INFRA-21234
<https://issues.apache.org/jira/browse/IN
Francis Chuang created CALCITE-3904:
---
Summary: Upgrade github actions dependencies
Key: CALCITE-3904
URL: https://issues.apache.org/jira/browse/CALCITE-3904
Project: Calcite
Issue Type
The error is caused by
private static final boolean USE_CANONICAL_HOSTNAME = true;
in
https://github.com/apache/calcite-avatica/blob/73fac75befaaf3caa3871656d0d0b7adbd91f7cf/core/src/main/java/org/apache/calcite/avatica/remote/AvaticaCommonsHttpClientSpnegoImpl.java#L58
In other words,
It's strange that you see this on Windows. Everything should be using
localhost in the tests. Maybe that means it's something specific to
Windows? I don't know enough to say if that's a reasonable guess or not.
The principal looked up stems from the hostname you issue a request to.
e.g. if
>localhost but the principal being looked up is FQDN.
Where that FQDN is taken from?
Vladimir
ttps://github.com/apache/calcite-avatica/blob/master/server/src/test/java/org/apache/calcite/avatica/SpnegoTestUtil.java#L58
> does
> localhost but the principal being looked up is FQDN.
> Kevin Risden
>
>
>
> On Sun, Nov 10, 2019 at 4:53 PM Vladimir Sitnikov <
> sitnikov.v
s://github.com/apache/calcite-avatica/blob/master/server/src/test/java/org/apache/calcite/avatica/SpnegoTestUtil.java#L58
does
localhost but the principal being looked up is FQDN.
Kevin Risden
On Sun, Nov 10, 2019 at 4:53 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> Hi,
Hi,
I've added GitHub Actions for CI, and it looks like AvaticaSpnegoTest fails
again.
The failure is the same for Maven and Gradle, so I expect it is not caused
by Gradle migration
Maven: https://github.com/vlsi/calcite-avatica/runs/296688961#step:4:31296
Gradle:
https://github.com/vlsi
>Definitely would simplify some of
>the RM steps for a release.
I've recently added GitHub Actions config to test Apache JMeter for Windows
and macOS.
So far I'm impressed.
Pros:
* It starts quite fast. Appveyor might take 2-3hours to even start the
build.
Actions start very fast, and i
. Definitely would simplify some of
the RM steps for a release.
Kevin Risden
On Tue, Sep 17, 2019 at 7:20 PM Francis Chuang
wrote:
> A month or so ago, I started a thread on Github Actions on the list. I
> have just replaced Travis with Github Actions for Avatica-Go
> (CALCITE-3356).
A month or so ago, I started a thread on Github Actions on the list. I
have just replaced Travis with Github Actions for Avatica-Go (CALCITE-3356).
For the workflows in Avatica-Go (currently just 1 for CI), see:
https://github.com/apache/calcite-avatica-go/tree/master/.github/workflows
Francis Chuang created CALCITE-3356:
---
Summary: Use Github Actions for continuous integration
Key: CALCITE-3356
URL: https://issues.apache.org/jira/browse/CALCITE-3356
Project: Calcite
.
Best,
Stamatis
On Tue, Aug 20, 2019 at 1:24 PM Michael Mior wrote:
> Sounds great! I've been wanting to play around with GitHub Actions
> more myself and this sounds encouraging.
> --
> Michael Mior
> mm...@apache.org
>
> Le lun. 19 août 2019 à 18:15, Francis Chuang
>
Sounds great! I've been wanting to play around with GitHub Actions
more myself and this sounds encouraging.
--
Michael Mior
mm...@apache.org
Le lun. 19 août 2019 à 18:15, Francis Chuang
a écrit :
>
> Hey everyone,
>
> Previously I mentioned that I was working on automated we
into a few issues:
- I couldn't get a Jenkins build to trigger only when a new tag that
matches a regex is pushed.
- The jenkins build can sometimes be unreliable and not trigger.
Recently, Github released Github Actions, which allows not just CI/CD,
but the ability to run any piece of code
26 matches
Mail list logo
