Skip to content

Point the build at develocity.apache.org and update the Develocity extensions - #133

Open
clayburn wants to merge 1 commit into
apache:masterfrom
clayburn:develocity-apache-org
Open

clayburn wants to merge 1 commit into
apache:masterfrom
clayburn:develocity-apache-org

Conversation

@clayburn

Copy link
Copy Markdown

Description

The build is configured to publish to https://ge.apache.org. That hostname should now be develocity.apache.org. This points the build at https://develocity.apache.org and moves to the current extensions.

Extension versions

gradle-enterprise-maven-extension 1.19.2 → develocity-maven-extension 2.5.0 (the artifact was renamed), and common-custom-user-data-maven-extension 1.12.4 → 2.4.0.

Configuration schema

.mvn/gradle-enterprise.xml.mvn/develocity.xml, with the two elements the Develocity schema renamed:

  • goalInputFilescapture/fileFingerprints
  • publish=ALWAYS + publishIfAuthenticated=truepublishing/onlyIf=authenticated (an exact translation of the previous behaviour)

This PR has:

  • been self-reviewed.
  • added or updated version, license, or notice information

Key changed/added classes (or packages if there are too many classes) in this PR
  • .mvn/extensions.xml
  • .mvn/develocity.xml (renamed from .mvn/gradle-enterprise.xml)

The build publishes to https://ge.apache.org, which no longer serves TLS
for that hostname: the handshake is reset, so every build fails to contact
the server. No build scan has arrived since 2024-12-18.

Point the build at https://develocity.apache.org, rename the extension to
develocity-maven-extension 2.5.0, bump common-custom-user-data-maven-extension
to 2.4.0, and translate the configuration to .mvn/develocity.xml under the
Develocity schema, which renamed two elements:

  goalInputFiles                    -> capture/fileFingerprints
  publish + publishIfAuthenticated  -> publishing/onlyIf = authenticated

Both workflows already export DEVELOCITY_ACCESS_KEY, which only the
Develocity extension reads, so CI authentication could not have worked
before this change either.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, this is your first pull request in IoTDB project. Thanks for your contribution! IoTDB will be better because of you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant