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
For whatever reason, randomly the step of deploying can hangs forever whereas the deployment is effective on Clever Cloud. Does anyone has encountered this issue?
I'm using:
- name: Deploy to Clever Clouduses: 47ng/[email protected]with:
appID: ${{ env.CLEVER_APP_ID }}force: truequiet: true # disable copying into GitHub Actions all logs from Clever Cloudenv:
CLEVER_TOKEN: ${{ secrets.CLEVER_TOKEN }}CLEVER_SECRET: ${{ secrets.CLEVER_SECRET }}
I have to cancel my run after X hours to free my pipeline. Note in a normal situation it takes around 5 minutes to deploy.
A solution to mitigate freezing the pipeline would be to add something like timeout-minutes: 15 to the step so it warns us to check the deployment has worked or not.
Thank you,
The text was updated successfully, but these errors were encountered:
There is a timeout option, although I've been seeing successful deployments failing to mark the step as complete and keeping running until that timeout occurs, I'll have to investigate.
Any news on this issue? The timeout option doesn't seem to be taken into account either. Thanks
I realised that the CI worked on one of my projects but not on the other, even though they are similar. The only difference was that I was using actions/checkout@v4 on the one that wasn't working and actions/checkout@v3 on the one that was. I switched back to v3 on the first one and it's working again.
Hi,
For whatever reason, randomly the step of deploying can hangs forever whereas the deployment is effective on Clever Cloud. Does anyone has encountered this issue?
I'm using:
I have to cancel my run after X hours to free my pipeline. Note in a normal situation it takes around 5 minutes to deploy.
A solution to mitigate freezing the pipeline would be to add something like
timeout-minutes: 15
to the step so it warns us to check the deployment has worked or not.Thank you,
The text was updated successfully, but these errors were encountered: