Enable Build Scans on develocity.commonhaus.dev#2543
Conversation
kdavisk6
left a comment
There was a problem hiding this comment.
I'm still getting back up to speed here. I'm assuming this is part of the projects enrollment in the Commonhaus Foundation and this is one of the benefits, considering Develocity is a pay service?
@kdavisk6, correct. Its a way to get some observability/metrics into your build. What takes the longest, track flaky tests, compare builds to see what changed between them (dependencies, java version, etc). |
|
Great. I'll approve the PR, but wait to test the workflows until we get the Secret configured. |
Previous commit added a secret using an incorrectly formatted YAML file
|
Looks like there was a YAML formatting error: Fixed in: 41f3cc9 |
* Enable Build Scans on develocity.commonhaus.dev * Correcting error in codeql-analysis workflow Previous commit added a secret using an incorrectly formatted YAML file
* Enable Build Scans on develocity.commonhaus.dev * Correcting error in codeql-analysis workflow Previous commit added a secret using an incorrectly formatted YAML file
cc: @velo
Note
This repo (or org) will need a secret named
DEVELOCITY_ACCESS_KEY(This was recently done for Morphia, the process should be the same here.)