raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10
27486 commits 1 branch 31 tags 268 MiB
Commit graph

4 commits

Author SHA1 Message Date
Clay Johnson
4a73fd9be0
Publish build scans to develocity.apache.org (#1718) 
* Publish build scans to develocity.apache.org

* Use `DEVELOCITY_ACCESS_KEY` to authenticate to `develocity.apache.org`
 2025-01-15 00:20:07 +01:00
Clay Johnson
2698511938
Disabled Develocity local build cache (#1512) 
sbt-develocity v1.1 ships with local and remote build cache support for the
`compile` and `test` tasks (see
https://gradle.com/develocity/releases/2024.2#build-caching-for-sbt).

The local build cache is enabled by default, while the remote cache requires
configuring the nodes that are allowed to upload artifacts to the build cache
(see
https://docs.gradle.com/develocity/sbt-build-cache/#rolling_out_the_cache_in_your_organization).

It's important to confirm that a project's build is ready to use the build cache
(local or remote) to avoid unexpected behaviors. Specifically, one should make
sure that all relevant inputs to the `compile` or `test` task are captured, as
otherwise the generated build cache key will be incorrect (this can lead to
erractic behavior, as entries from the cache will be reused when they
shouldn't). Refer to
https://docs.gradle.com/enterprise/sbt-plugin/#caching_the_compile_task to know
what are the build cache inputs captured for the `compile` task and
https://docs.gradle.com/enterprise/sbt-plugin/#caching_the_test_testonly_and_testquick_tasks
for the `test` task.

This commits disables the local build cache so that a proper rollout can be
planned (see
https://docs.gradle.com/develocity/sbt-build-cache/#rolling_out_the_cache_in_your_organization).

Co-authored-by: Mirco Dotta <mdotta@gradle.com>
 2024-10-02 11:23:20 +02:00
Martin Duhem
54ff1fcf1f
Configure TestJdk9 for Develocity (#1370) 
Prevously, the tests that are run in the `TestJdk9` configuration were
not captured by Develocity: the results of these tests would not appear
in the Develocity test report and dashboard, and failed tests would not
be retried.

Because TestJdk9 is a custom configuration, Develocity cannot configure
it automatically and we need to manually add the Develocity test
settings in that configuration. This is done through an auto plugin that
is enabled only on projects where both the Develocity and Jdk9 plugins
are enabled.
 2024-06-17 17:21:01 +01:00
Alexey Venderov
763cdb64eb
Capture build scans on ge.apache.org to benefit from deep build insights (#1288) 
* Capture build scans on ge.apache.org to benefit from deep build insights (#1)

* Add Develocity plugin and configure it to publish to Apache Develocity instance

* Add Develocity access token to CI jobs

* Use convention plugin to configure Develocity

* Add opt-in property

* Revert "Add opt-in property"

This reverts commit ff556b9764fd6b980b24082a3195ba3fbd22faf6.

* Improve variable name

* Use upper case i in CI abbreviation
 2024-04-25 17:25:52 +02:00