jitpack.io download seems to be unstable

[MarkusTiede]

[juliafeld]

Probably this was the original error that we got.

[culmat]

Hi Julia,

can you please run powershell -Command "Set-PSDebug -Trace 2; $proxy = [System.Net.WebRequest]::GetSystemWebProxy();$proxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials;$wc = new-object system.net.WebClient;$wc.proxy = $proxy;$wc.DownloadFile('https://jitpack.io/com/github/baloise/proxy/main-SNAPSHOT/proxy-main-SNAPSHOT.jar', '%tmp%/proxy.jar');"

and share the output. I hope to get some more insight on the error.
Thanks & regards.
Matthias

[culmat]

Jitpack has been running stable from our experience.
As of https://status.jitpack.io/ the uptime > 99%

[culmat]

Further analysis of today.

https://jitpack.io/com/github/baloise/proxy/win64-SNAPSHOT/proxy-win64-SNAPSHOT.jar
redirects to https://jitpack.io/com/github/baloise/proxy/win64-84ea280527-1/proxy-win64-84ea280527-1.jar
which responds "File not found. Build ok", The same response is obtained for https://jitpack.io/com/github/baloise/proxy/win64-84ea280527-1/build.log

The download had worked for the past few weeks pointing to the commit hash 0eff7ec

Download via the commit hash works https://jitpack.io/com/github/baloise/proxy/0eff7ec2bcb6f7d42df5554692012824c70e4337/proxy-0eff7ec2bcb6f7d42df5554692012824c70e4337.jar by triggering a fresh build with, see https://jitpack.io/com/github/baloise/proxy/0eff7ec2bcb6f7d42df5554692012824c70e4337/build.log

After triggering the rebuild via the commit hash, the links containig win64-84ea280527-1 start to wirk again.

Expected behaviour: if a file is missing ( cleaned up? ) it should be (re)build, aka jitpackaged ;-)

see also jitpack/jitpack.io#3295