-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
staged recipes broken on travis 403 errors #10438
Comments
This looks identical to #5846 with the error response:
|
Yep. Not sure it is related to that. @isuruf and @mariusvniekerk, do you have an idea on how to debug this? |
Bump here @conda-forge/core. I know we are all very busy, but any help you can provide would be appreciated! |
Looks like @chrisburr moved us back to .org and this fixed things. I guess this means this is an upstream issue with Travis? |
the keys encrypted for .org and .com are not compatible. |
@ocefpaf is writing Travis to see if this is a bug on their end. |
It's not a travis-ci issue anymore. |
I’m not following but glad you all are on it. Thanks! |
Now we are getting drone errors. I guess we need to go through and reencrypt all of the keys or something?
|
This appears resolved. Thanks @ocefpaf! Closing! |
Alright @conda-forge/core @conda-forge/staged-recipes, it appears that staged-recipes will be broken until someone can diagnose the 403 error we are getting on travis-ci.com.
It appears that when we ask travis-ci.com to make sure repos build only with yaml here in conda-smithy, we are getting a 403 HTTP code, meaning we don't have permission.
@ocefpaf tried to reset update the permissions/keys/whatever, but it is still not working.
Can someone on @conda-forge/core look into this? I think you all are the only ones with keys.
The text was updated successfully, but these errors were encountered: