This method allows custom contexts to pick the behavior they want when
a class contains getters/setters that do not have a matching field,
making enhancement impossible.
Three behaviors are available:
* SKIP (the default), which will skip enhancement of such classes.
* FAIL, which will throw an exception upon encountering such classes.
* LEGACY, which will restore the pre-HHH-16572 behavior.
I do not think LEGACY is useful at the moment, but I wanted to have
that option in case it turns out HHH-16572 does more harm than good in
Quarkus 3.15.
Don't tar them, as this was broken: we ended up uploading the
build-scan-data directory instead of the tar, while still expecting a
tar when dowloading, which made everything fail.
We don't need tars anyway, as workflow artifacts are already zipped.
(cherry picked from commit 6551aa59c592b021c4ad3ebab31684d34311e5d7)
We don't need the whole cache, since most (all?) of it is stored on
Develocity already.
Including ./gradle/caches/modules-2 is enough, because that's where
Maven dependencies are stored, and *those* are not stored on Develocity.
(cherry picked from commit 013bb46470f97285ae57190c9ce5201f31105a21)
Ripped off from Quarkus.
Here's how it will work:
1. We create a cache entry on push only. Pull requests only restore it.
2. We create a new cache entry every day, prefixed with something like
2024-10-25.
3. When restoring the cache, we try the entry for the day first
(2024-10-25) and default to the one for the month (2024-10-*).
Critically, this means we will build each day's cache based on the
previous day's cache.
4. Atlas infra uses its own, separate cache entries.
Co-Authored-By: Guillaume Smet <guillaume.smet@gmail.com>
(cherry picked from commit 5eaaff2e6367fd4f1071a90eba2e274c800629cd)
So that we're extra sure we're not relying on cache left by a previous
Gradle execution.
(cherry picked from commit 543e095cf70396256ebbf2dd9e9d07f80304bebd)
* Use `pull_request` instead of `pull_request_target`
* Move Develocity build scan publishing for untrusted code to a separate workflow
* Merge Atlas workflow into the main CI workflow
* Split caches between trusted and untrusted code
* Update secrets to use "Develocity" name instead of "Gradle Enterprise"
* Update comments
Co-Authored-By: Yoann Rodière <yoann@hibernate.org>
(cherry picked from commit df8b16369f9d5bd890b889df02b0082960330b64)
On CockroachDB the method
`testCopyPersistentCollectionReferenceAfterFlush` causes a
deadlock, which is resolved eventually by a TimeoutException.
This problem has been discussed in
https://github.com/cockroachdb/cockroach/issues/61269. The
CockroachDB developers do not see this as a bug that needs to
be fixed. Therefore we skip this test for CockroachDB.
