-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Permission request for https://ci.adoptopenjdk.net/ #2722
Comments
Access granted to |
verified: abort, create new, check config these all work for me now |
I found out I still miss permission to run VPC
from https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1535/consoleFull |
Try now - that should not have been restricted :-) |
rerun the same build, but still hanging there https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1537/
it is not urgent, can check later when you are back :D |
Any procedure need to follow to get permission for https://ci.adoptopenjdk.net/job/build-scripts/job/release/ ? |
@sxa Will this require a request to the EF? |
@karianna No as it's still controlled via the AdoptOpenJDK github org. |
OK I have no idea why that's happening. I've tried a few things to no avail. It doesn't seem to be working with groups. Have opened #2778 to investigate. |
Any way can proceed with this permission? |
@zdtsw Which permissions are still required? |
@karianna It'll be adding to |
That team doesn't seem to exist? |
Invited to the relevant groups - may need to check your inbox or GitHub homepage to accept the invites |
awesome! 👍 got the mails + did a logout then login to the jenkins |
I'll close this now (As mentioned the VPC access will need to be dealt with separately as it's being weird). If anything else shows up during the release cycle please reopen this. |
I would like to get permission in https://ci.adoptopenjdk.net/
The text was updated successfully, but these errors were encountered: