It's tricky - have to use a mixture actually, as I notes in https://github.com/apache/polaris/pull/475#issuecomment-2497792648 : "Apache's instance rejects unauthenticated build scans, which is always the case for PR CI runs (no secrets in those GH workflows). So I think it's fine to let CI runs that don't have the access-key secret publish to Gradle's infra, and those that have it publish to Apache's infra."

On 25.11.24 12:39, Eduard Tudenhöfner wrote:
I think that's a good idea, so +1 from my side.

On Mon, Nov 25, 2024 at 11:10 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote:

    Hi folks,

    The ASF is hosting a Gradle Develocity instance where we can store our
    build scans.

    It's hosted on https://ge.apache.org.
    Several projects are using it (Apache Beam, Apache Pekko, etc).

    Build scans collect information about a build, including the actual
    output of failed tests.
    It's convenient to investigate test failures (in our GH Actions) and
    Gradle plugins executions.

    I'm proposing to export/store our build scans on ASF Develocity.

    Thoughts ?

    Regards
    JB

--
Robert Stupp
@snazy

Reply via email to