jitpack
Webhook to trigger builds on custom domains
Is your feature request related to a problem? Please describe. The existing webhook feature works well for the case of com.github.user as groupId. But doesn't trigger build for custom domain case.
Describe the solution you'd like A webhook that can be used, such as from a GitHub workflow, that can trigger a build for a custom domain setup. Or some other mechanism to accomplish this.
Describe alternatives you've considered I hacked together a way to use curl that sort of works but is less than ideal. See this workflow that runs on pushes to main and uses curl to request main-SNAPSHOT on the custom domain. It uses a 30 second timeout to avoid waiting for build. Most of the time that seems long enough but not always. But 30 seconds is less than ideal. Anything less seems very inconsistent in effectiveness.
I have a similar trick for releases in my deployment workflow. See the step that starts here.
This issue is stale because it has been open for 30 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Is JitPack maintained anymore? It seems to still run and serve artifacts but many issues without any triage for months and in some cases longer.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
To anyone stumbling upon this issue: It appears as if jitpack is no longer maintained. No PRs merged in the past 2 years. No maintainers comment or otherwise respond to issues. Thousands of issues that close automatically after 30 days.
I'm closing this issue, not because it was completed, but because I no longer care, and have removed all jitpack related configuration from my repositories since I can't depend upon what appears to be an abandoned project. Jitpack was a good service while it was maintained. But unfortunately that doesn't appear to be the case any longer.