search

afiore / action-allure-report

Github action to generate an Allure report
8 stars 10 forks source link

Bintray is going away and are deliberately causing errors #2

Open simonwo opened 3 years ago

simonwo commented 3 years ago

Hi there,

As the Bintray service is closing, they are deliberately scheduling brown-out times to alert their users: https://status.bintray.com/incidents/4mzph0y8l6hk

This is causing issues for any workflow using the allure report action as it fails to download the binaries. This will presumably become a permanent problem on May 1st.

Is there a plan to stop using Bintray for hosting?

Cheers.

andyhd commented 3 years ago

@afiore I think this is fixed by simply changing the ALLURE_REPO URL in the Dockerfile.

QuintilianoNery commented 3 years ago

Estou passando pelo mesmo problema, esse repositório Bintray está retornando forbiden 403. Acredito que a correção seria somente alterar a URL no docker file ALLURE_REPO para https://repo.maven.apache.org/

I'm experiencing the same problem, this Bintray repository is returning forbiden 403. I believe that the correction would only be to change the URL in the ALLURE_REPO docker file to https://repo.maven.apache.org/

@afiore

QuintilianoNery commented 3 years ago

@andyhd and @simonwo, you can use the following alternative that I just adjusted, nothing more than an adjustment to the URL of the Dockerfile

https://github.com/marketplace/actions/allure-report-v2

Based on the standard repository of @afiore.