Skip to content

[7.x] [Gradle] Remove jitpack repository usage #119053

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 19, 2024

Conversation

breskeby
Copy link
Contributor

Jitpack repository service is causing http errors resolving artifacts and we should not need it anyhow atm

jitpack is causing http errors resolving artifacts and we should not need it anyhow atm
@breskeby breskeby added >non-issue :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team v7.17.27 labels Dec 19, 2024
@breskeby breskeby self-assigned this Dec 19, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

Copy link
Member

@tlrx tlrx left a comment

Choose a reason for hiding this comment

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

LGTM with my limited knowledge of this area

@breskeby breskeby added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Dec 19, 2024
@breskeby breskeby changed the title [7.x] [Gradle] Remove jitpack usage [7.x] [Gradle] Remove jitpack repository usage Dec 19, 2024
@elasticsearchmachine elasticsearchmachine merged commit fa2883d into elastic:7.17 Dec 19, 2024
10 checks passed
@breskeby breskeby deleted the remove-jitpack-usage branch December 19, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v7.17.27
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants