[LMIT]v1.368.0 is breaking the CI/CD
Hi Team We are from Last Mile Testing Team We have automation suits to test BTP and BTP service and to find the regression before costumer faces the BTP service issue. We are blocked in it due to your latest release 15:27:20 ERROR: Download of Piper go binary failed. 15:27:20 Retrying 15:27:20 [Pipeline] { 15:27:20 [Pipeline] sh 15:27:20 + curl --insecure --silent --retry 5 --retry-max-time 240 --location --write-out %{http_code} --output piper https://github.com/SAP/jenkins-library/releases/latest/download/piper_master 15:27:21 [Pipeline] sleep 15:27:21 Sleeping for 10 sec 15:27:31 [Pipeline] error 15:27:31 [Pipeline] } 15:27:31 ERROR: Download of Piper go binary failed. 15:27:31 Retrying 15:27:31 [Pipeline] { 15:27:31 [Pipeline] sh 15:27:31 + curl --insecure --silent --retry 5 --retry-max-time 240 --location --write-out %{http_code} --output piper https://github.com/SAP/jenkins-library/releases/latest/download/piper_master
It is failing to download the piper binary
From the URL https://github.com/SAP/jenkins-library/releases/latest/download/piper_master
We see 404 error
Please have a look
Regards, Vinay C Uploading piperissue.txt…
Same here, all our pipelines are currently failing:
11:55:16 + curl --insecure --silent --retry 5 --retry-max-time 240 --location --write-out %{http_code} --output piper https://github.com/SAP/jenkins-library/releases/latest/download/piper_master
11:55:16 [Pipeline] echo
11:55:16 Not able to download go binary of Piper for version master
I don't see any update in ticket
Regards, Vinay C
Same issue open for me too : https://github.com/SAP/jenkins-library/issues/4972
Still no news
@C5324260 @i535489 Is the issue still there ? I could able to download the latest binary through this link https://github.com/SAP/jenkins-library/releases/latest/download/piper_master
Hi, Apparently nobody take care of issue here, i got information on slack that they removed the latest release, so it fix the issue as the 1.38 was breaking everything :)
closing this issue as we had reverted the release.
please note there are SAP specific channels where we update these issues and also fixes
the RCA was identified when concurrent builds happen during the release process and it copies and intermediate binary from current release which caused this issue.
for the future we are brining in a controlled release process where we first pre-release do some test and then release