gradle / gradle/develocity-build-validation-scripts
Unable to publish build scans to untrusted server without first modifying build
- Dominant language
- Shell
- Stars
- 115
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
Given a build not already configured with Develocity **_and_** a Develocity server with an untrusted certificate, then there is no way to run an experiment successfully without first modifying the build to [allow publishing build scans to an untrusted Develocity server](https://docs.gradle.com/enterprise/gradle-plugin/#allowing_untrusted_ssl_communication).
The `ssl.allowUntrustedServer` property in `network.settings` **only** configures the API call to allow making calls to an untrusted server, but not build scan publication itself. Therefore, the `-e` / `--enable-gradle-enterprise` option can only be used in cases where the Develocity server is already using a trusted certificate.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the `-e`/`--enable-gradle-enterprise` option and the `ssl.allowUntrustedServer` setting are handled. Verify the behavior for a build without Develocity configuration and a server with an untrusted certificate; done means an experiment can publish its build scan without modifying the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100