-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Our MacOS build logs are now hidden from everyone :-( #749
Comments
njsmith
added a commit
to njsmith/trio
that referenced
this issue
Oct 31, 2018
Since Jenkins is acting screwy and not letting people see the logs :-(. It's possible that this will cause python-triogh-584 to start happening again, so I guess we'll just have to watch out for that... Fixes python-triogh-749
njsmith
added a commit
to njsmith/trio
that referenced
this issue
Oct 31, 2018
Since Jenkins is acting screwy and not letting people see the logs :-(. It's possible that this will cause python-triogh-584 to start happening again, so I guess we'll just have to watch out for that... Fixes python-triogh-749
This seems to be going OK, so I've turned off Jenkins for now (I think). Notes: |
Apparently I only disabled one of the two places that Jenkins was hooked into the org settings. (I missed the webhook.) I've just disabled the webhook as well, so hopefully now it is actually disabled? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our macOS builds are currently done by a Jenkins instance maintained by the PyCA folks.
Unfortunately, something has changed so that now when you try to click on a link to view a build log, you get a 404. For example: https://ci.cryptography.io/job/python-trio/job/trio/job/PR-728/10/display/redirect
I asked @reaperhulk about this, and apparently it isn't due to any intentional configuration change, it's something that just started happening after the last time they upgraded jenkins. And apparently you can configure it not to do this but... it just ignores that configuration.
For the moment, I can see the build logs, because @reaperhulk gave me admin rights on the Jenkins, because apparently that is the only thing it actually respects. But this is not a workable long-term solution. We all need to be able to see the logs.
Unless we have some Jenkins whisperer who wants to volunteer their time here, I guess we need to move macOS builds to Travis or Azure.
The text was updated successfully, but these errors were encountered: