github-actions[bot] commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-2571488489
This PR has been closed since it has not had any activity in 120 days. If
you feel like this
was a mistake, or you would like to continue working on it, please feel free
to
github-actions[bot] closed pull request #15109: MINOR: Enable Gradle Remote
Build Cache
URL: https://github.com/apache/kafka/pull/15109
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific c
github-actions[bot] commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-2076286592
This PR is being marked as stale since it has not had any activity in 90
days. If you would like to keep this PR alive, please ask a committer for
review. If the PR has merge
clayburn commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1910737138
> Looks like Jenkins doesn't have permission (by default at least) to write
entries to the ASF Gradle Enterprise Build Cache:
This is correct. The reason for this is that we do not
divijvaidya commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1875475685
https://github.com/apache/beam/pull/27015 is not Apache Beam enabled this.
Seems like we need to request a build node from Apache Infra and change our
jenkins to pick up creds similar
nicktelford commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1875405401
Looks like Jenkins doesn't have permission (by default at least) to write
entries to the ASF Gradle Enterprise Build Cache:
```
Could not store entry 744bd685bdd1d149ec93934b276b
nicktelford commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1875356669
@ijuma I've temporarily reconfigured it to enable the cache for this branch
(`gradle-remote-build-cache`) instead of `trunk`, so we can test that it works
as expected using the CI bui
ijuma commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1874508632
I guess one way would be to enable the cache only for CI & trunk by default
at first. Then we could manually enable the cache locally and for one PR to
test the behavior. If it all looks go
ijuma commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1874507122
Could we do a test with a new branch (not trunk) where we validate the
behavior before we roll it out to everyone else?
--
This is an automated message from the Apache Git Service.
To res
nicktelford commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1874500874
Hi @divijvaidya , this enables the _remote_ build cache, which allows
different machines to share the cached output of tasks.
Thanks for the links to the builds, I haven't had a
divijvaidya commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1874483500
Hey @nicktelford , you don't need committer permissions to look at ASF
gradle. Try using this link: https://ge.apache.org, it should be publicly
accessible.
For this PR, here'
nicktelford commented on PR #15109:
URL: https://github.com/apache/kafka/pull/15109#issuecomment-1874134447
I don't have access to the ASF Gradle Enterprise, so a committer will need
to verify that this works as intended.
--
This is an automated message from the Apache Git Service.
To res
nicktelford opened a new pull request, #15109:
URL: https://github.com/apache/kafka/pull/15109
We enable the remote build cache, hosted by the ASF Gradle Enterprise
instance.
We only cache tasks during builds on `trunk`, to ensure that pushes to PRs
always re-run all Tasks needed by
13 matches
Mail list logo
