Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Too many requests" from GitHub's cache #66

Open
snazy opened this issue Mar 31, 2023 · 0 comments
Open

"Too many requests" from GitHub's cache #66

snazy opened this issue Mar 31, 2023 · 0 comments

Comments

@snazy
Copy link

snazy commented Mar 31, 2023

I tried the gradle-cache-action against some refactoring of our CI workflows. The amount of time spent in our CI went quite up (up to 70 minutes), so there's the idea to split the work into separate GH workflow jobs, but should leverage Gradle caching. I ended up with nearly 20 jobs in that workflow to get CI time back to the ~20 minutes target.

However, with that amount of jobs, basically every Gradle build complains with, which I think effectively says that GitHub "doesn't like that many requests".

Error: Cache service responded with 429
    at /home/runner/work/_actions/burrunan/gradle-cache-action/v1/dist/cache-action-entrypoint.js:222:74
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/burrunan/gradle-cache-action/v1/dist/cache-action-entrypoint.js:138:23)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Is there anything that could be done to issue less requests against GH's cache?

Otherwise I'd have to go back to gradle-build-action, with some (not so nice) hacks to collect the build-cache modifications, push those as artifacts around and so on. The gradle-cache-action looks so much nicer and cleaner to me.
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
10e7068 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just auto-labeling for PRs (or nothing for main)
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.)

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
c11aabf 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just auto-labeling for PRs (or nothing for main)
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.)

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
71b0b99 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just auto-labeling for PRs (or nothing for main)
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.)

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
f332bf5 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just auto-labeling for PRs (or nothing for main)
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.)

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
83710e1 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just auto-labeling for PRs (or nothing for main)
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
823dd98 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just auto-labeling for PRs (or nothing for main)
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
409dc11 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 4 "stages":
* Prepare - this is just a "starter mark"
* Checks - test, intTest, NesQuEIT, etc
* Finalize

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
df8ecb6 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
3b3536d 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
af23dd6 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
a7e8d44 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
1b088d9 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
2bc0bf2 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
1cccdf6 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
e290ed7 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
95fd62c 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
276478e 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
@snazy snazy mentioned this issue Apr 1, 2023
Merged
snazy added a commit to snazy/nessie that referenced this issue Apr 1, 2023
@snazy
Refactor CI workflow
83c19dd 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
0f32a43 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
6a6401d 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
345f833 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
1fec668 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
4346a19 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
d65924c 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
c191fb5 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 2, 2023
@snazy
Refactor CI workflow
2a70f45 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to snazy/nessie that referenced this issue Apr 3, 2023
@snazy
Refactor CI workflow
47d2aca 
Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes projectnessie#6365
snazy added a commit to projectnessie/nessie that referenced this issue Apr 3, 2023
@snazy
Refactor CI workflow - bring back reasonable CI runtime (#6461)
3bd3911 
Refactor CI workflow

Unifies most main + PR workflows into a single workflow.

The unified CI workflow consists of 2 "stages":
* Checks - test, intTest, NesQuEIT, etc
* Finalize - a "success" dummy job + a "save to github-cache" job

Utilizes the Gradle build cache for all stages. The updated build cache
of the jobs in the checks stage are saved as artifacts (with the minimum
retention period). The updated build cache is pushed back to GigHub's
cache when the checks have successfully finished.

Java CI runs against Java 11 and Java 17, where it is meaningful.
(Spark + Deltalake tests always run against 11, so not run against
Java 17.) Some checks also run against the latest Java version.

Codecov was not added to the new workflow, it wasn't working for quite
a while now or produced wrong results.

Build logs and reports are not archived. Test results and relevant logs
are available via Gradle build scans.

Windows + macOS workflows are not included in the unified workflow.

There is also another [Gradle cache
action](https://github.com/burrunan/gradle-cache-action), which utilizes
the GitHub's cache like a remote Gradle cache. However, that puts too
much load (requests) against GitHub's cache, which in turn throttles our
CI and responds with HTTP/429 (Too many requests). See [this
issue](burrunan/gradle-cache-action#66).

Fixes #6365
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@snazy