You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A significant feature introduced in 0.6.9 and still referenced in the README was that the action no longer installed Python by default. This was necessary to be able to run the action on Alpine and other OSes, which have various problems with having Python installed by an action.
This was broken in #63 which was included in v0.6.12 of this action. So once again it does not work on other OSes. (I suspect the problem is glibc versions.)
I build packages on the OS they are targeted for so that I can test them by installing the package and running the tool(s) installed. I do not want to have to export that package somewhere and then download it to Ubuntu in order to upload it to Cloudsmith.
Please make an option to not use Python again, and fix the README.
Side note regarding curl failures
The reason I tried to upgrade from v0.6.10 was that a significant number of actions failed on the line
I suspect the failure was due to rate limiting, but it could be due to some other transient error. This could be mitigated by using --retry 4.
This could also be mitigated by using a hard-coded URL that points to your infrastructure and which you update to redirect to the latest version as part of the release process.
The text was updated successfully, but these errors were encountered:
A significant feature introduced in 0.6.9 and still referenced in the README was that the action no longer installed Python by default. This was necessary to be able to run the action on Alpine and other OSes, which have various problems with having Python installed by an action.
This was broken in #63 which was included in v0.6.12 of this action. So once again it does not work on other OSes. (I suspect the problem is
glibc
versions.)I build packages on the OS they are targeted for so that I can test them by installing the package and running the tool(s) installed. I do not want to have to export that package somewhere and then download it to Ubuntu in order to upload it to Cloudsmith.
Please make an option to not use Python again, and fix the README.
Side note regarding
curl
failuresThe reason I tried to upgrade from v0.6.10 was that a significant number of actions failed on the line
download_url=$(curl --silent "https://api.github.com/repos/cloudsmith-io/cloudsmith-cli/releases/latest" | jq -r '.assets[0].browser_download_url')
I suspect the failure was due to rate limiting, but it could be due to some other transient error. This could be mitigated by using
--retry 4
.This could also be mitigated by using a hard-coded URL that points to your infrastructure and which you update to redirect to the latest version as part of the release process.
The text was updated successfully, but these errors were encountered: