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
CircleCI is changing a few things around artifact management, and according to this email we are affected. I haven't investigated what exactly needs to be done, but here's the issue for us to discuss it.
CircleCI's message
Hi there,
We’re writing to let you know about two upcoming changes to build artifacts that you can expect to see in the coming month. We’re making these changes in an effort to improve the performance of our artifacts hosting, make build artifact downloads faster and more reliable, and reduce security risks for our users.
The key changes you can expect to see are:
Build artifacts redirects: we are making non-HTML build artifacts on CircleCI redirect to short-lived pre-signed cloud storage URLs to improve the performance of our artifacts hosting.
If you are using a web browser to view HTML resources such as test/coverage reports or download tarballs/zip files, you will not need to change anything.
If you are using curl or another HTTP client that does not follow redirects by default, you will need to enable redirect support. For curl, you’ll need to add an `-L ` flag. For other HTTP clients please check the docs for specific redirect set up instructions.
Any projects you are associated with using curl are listed below.
[https://github.com/scikit-learn/scikit-learn]
Build artifacts storage policy: beginning on April 30th, we will start automatically deleting build artifacts that are older than 30 days for paid & free accounts. To download your older build artifacts before then, follow these instructions. Note that this policy change will not impact other CircleCI output data such as caches, workspaces, and logs.
If you have any questions or concerns about the scope or impact of these changes, please submit a support ticket through the CircleCI Support Center.
Thanks,
The CircleCI Engineering Team
The text was updated successfully, but these errors were encountered:
Reviewing our scripts for circleci, I do not see an issue with this.
Maybe circleci greped the repo for "curl" and pushed that email. The places where we use curl is in travis_fastfail.sh and in github actions. This should not influence how we use circleci.
CircleCI is changing a few things around artifact management, and according to this email we are affected. I haven't investigated what exactly needs to be done, but here's the issue for us to discuss it.
CircleCI's message
Hi there,
We’re writing to let you know about two upcoming changes to build artifacts that you can expect to see in the coming month. We’re making these changes in an effort to improve the performance of our artifacts hosting, make build artifact downloads faster and more reliable, and reduce security risks for our users.
The key changes you can expect to see are:
If you have any questions or concerns about the scope or impact of these changes, please submit a support ticket through the CircleCI Support Center.
Thanks,
The CircleCI Engineering Team
The text was updated successfully, but these errors were encountered: