Use Access Key based authentication via Develocity Connector #673
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This migrates the access to the Develocity Build Cache to use Access Key based authentication instead of username and password authentication. This means that the access will use the same access key as is is used for Build Scan publication. Here is more information on the Develocity Connector [see here](https://docs.gradle.com/enterprise/gradle-plugin/#using_the_develocity_connector)
a2c71e9 to
8dfe7f2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
This migrates the access to the Develocity Build Cache to use Access Key based authentication instead
of username and password authentication. This means that the access will use the same access key as is
is used for Build Scan publication.
Here is more information on the Develocity Connector see here
Testing
Test: This should be tested post merge on a CI job that has a proper access key with permission to push to the remote build cache.
This fork does not have the correct credentials.
I did test proper build scan publication against another Develocity instance.
Issues Fixed
Fixes: [Optional] The bug on https://issuetracker.google.com being fixed