Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #12703
| From | Sean Gilligan <sean@msgilligan.com> |
|---|---|
| Newsgroups | linux.debian.maint.java |
| Subject | Using Gradle Build Scans™ with Debian Gradle 4.4.x |
| Date | 2023-09-28 20:10 +0200 |
| Message-ID | <Hj3Cy-cbss-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Although Build Scans™ are a proprietary add-on to Gradle, they are very useful in a FOSS CI environment. They make it very easy to find all the information you need to troubleshoot a failing build or find ways to optimize build scripts. Unfortunately, the options for agreeing to the terms-of-service in a CI environment have been difficult to configure cleanly. (You also have to give them your email, which I don't mind doing but some may object.) I opened an issue with Gradle about programmatically agreeing to the TOS and Stefan Wolf from Gradle provided an initialization script that solves the problem: https://github.com/gradle/gradle/issues/26316#issuecomment-1739245349 The script works with Gradle 4.4.x (FrankenGradle) through 8.x (at least.) The nice thing about this solution is that the script lives in a separate file and is only activated with specific command line options: `--init-script build-scan-agree.gradle --scan` I've tested it with bitcoinj and created two PRs that use it. They provide examples of how to use it: GitHub Actions: https://github.com/bitcoinj/bitcoinj/pull/3289 GitLab CI: https://github.com/bitcoinj/bitcoinj/pull/3290 Regards, Sean
Back to linux.debian.maint.java | Previous | Next | Find similar
Using Gradle Build Scans™ with Debian Gradle 4.4.x Sean Gilligan <sean@msgilligan.com> - 2023-09-28 20:10 +0200
csiph-web