Skip to content

Validate wrappers for all Gradle nightlies published at https://services.gradle.org/distributions-snapshots/Β #281

Closed

Description

@eskatos

This is a prerequisite for using the action in any repository that makes use of nightlies.

This is a prerequisite for dogfooding in the gradle org which makes heavy use of nightlies.

Currently, the action consumes https://services.gradle.org/versions/all which contains information about the latest nightly and the latest release nightly only. All other nightlies are missing.

Activity

  1. assigned and unassigned on Jul 19, 2024
  2. 3flex commented on Jul 22, 2024

    @3flex
    Contributor

    The services.gradle.org versions API only provides details on latest nightly (and release nightly), so wouldn't the API need to be enhanced first? Is there another source for this?

  3. bigdaz commented on Jul 22, 2024

    @bigdaz
    Member

    While not ideal, it should be possible to extract the wrapper checksums by traversing the directory listing at https://services.gradle.org/distributions-snapshots/

  4. 3flex commented on Jul 22, 2024

    @3flex
    Contributor

    Do you mean by reading the HTML and looking for the links? Or is there another way? I'd have thought that would be a little fragile, and failures to parse would have to fail the action if validation has been enabled (though given it's for nightlies failures are relatively lower impact, and any issue would surely be fixed quickly especially if it's impacting Gradle's own builds).

    I'm not volunteering to build a PR since I'm unfamiliar with TypeScript but the pointers might help someone with the right experience. It would be nice to unblock #12 for v4.

  5. bigdaz commented on Jul 22, 2024

    @bigdaz
    Member

    Yes, that's what I meant. The HTML is a generated directory listing and should be generally stable over time.

    We would only fail the build if all of the following were true:

    I think this would be acceptable.

    I'm not sure about getting #14 into v4, but you're right that it would be nice.
    I now wish I'd released v4.0.0-beta.1 instead of going straight to an RC!

  6. added this to the v4.0.0 milestone on Jul 22, 2024
  7. added 2 commits that reference this issue on Jul 31, 2024
    ca81ef2
    7179909
  8. added a commit that references this issue on May 30, 2025
    2109c1e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions