Commit Graph

10 Commits

Author SHA1 Message Date
Yoann Rodière b34462138d Remove non-fonctional "JOB_NAME" custom value in build scans
It doesn't seem to work as we get "JOB null" on every build scan.
Even if it worked, it would most likely only display the top-level job,
e.g. `hibernate-orm-pipeline` on Jenkins, which doesn't give much
information.
2024-03-21 10:59:24 -05:00
Yoann Rodière bc14ea52eb Add more tags to build scans 2024-03-21 10:59:24 -05:00
Steve Ebersole b771afda5b Populate remote Gradle build cache from CI jobs 2024-01-19 11:58:41 -06:00
Steve Ebersole 92b46bca5b Gradle build clean-ups
- drop use of `allprojects`
2022-03-15 09:39:07 -05:00
Steve Ebersole 662182adff Gradle Enterprise - remote build cache 2022-03-03 15:45:41 -06:00
Steve Ebersole f618b47db4 HHH-14634 : Gradle Enterprise
- re-enable `publishAlways` in addition to `publishIfAuthenticated`
2021-06-11 11:28:09 -05:00
Steve Ebersole 2967f6b40b HHH-14634 : Gradle Enterprise
- temporarily move `publishAlways` to just CI runs until Gradle can clarify how to use that when users are not authenticated; I was originally told that `publishAlways` would simply skip publishing if credentials are not present, but that is clearly not the case
2021-06-11 10:20:34 -05:00
Steve Ebersole cbeedd1c32 HHH-14634 : Gradle Enterprise
- added JDK version as tag
- added job-name (for CI) as tag
2021-05-26 12:36:59 -05:00
Steve Ebersole 1238e5261d HHH-14634 : Gradle Enterprise
- removed older "build scan recipes" plugin
- adjusted CI handling based on feedback
2021-05-25 16:39:52 -05:00
Steve Ebersole 63c10e8ec0 HHH-14634 : Gradle Enterprise
- extracted config into `gradle-enterprise.gradle` to help move config to other branches/projects
2021-05-24 12:25:53 -05:00