-
-
Notifications
You must be signed in to change notification settings - Fork 169
Jenkins access for CitGM team #584
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
Comments
This would be really useful |
sounds good to me. |
+1 from me |
@mhdawson do you have the permissions to give us access to the CI or do we need to CC someone else? |
I'm looking at it right now :). If you are around I'll ping you in a few minutes to see if you can try it out for me. |
@mhdawson I'm on slack for the next hour or so :) |
Ok as per doc, access to start jobs has been grated to all members of the citgm team. Will now setup citgm-admin team, add Myles as initial member and let citgm team use process to nominate others that will be able to create/modify jobs. |
Ok, create citgm-admins and the 4 CITGM jobs are now configured so that they can be created/modified by the members of that group. Initially I've made Myles the only member of the group. |
Ok, CITGM team went through process and George is now in the citgm-admins group and seems to be able to edit jobs. Going to close this and we can reopen if something more is required. |
Now that #554 has landed we can start giving teams access to their Jenkins jobs. For the CitGM team the jobs beginning with
citgm-
are the ones that the CitGM team should have permissions for. If no-one objects we should set the run/modify permissions for these jobs to the @nodejs/citgm team.Jobs:
People in the citgm team:
The text was updated successfully, but these errors were encountered: