-
Notifications
You must be signed in to change notification settings - Fork 135
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
Create 2 new repositories for build wg - jenkins config #464
Comments
+1. What teams will have write or admin access? |
@nodejs/tsc @nodejs/community-committee |
Initially, they will be private repos. They will be readable by nodejs/build, and writable by a jenkins backup cron job. Intention is that when we validate that no sensitive information is in the build job XML, they become public, readable by all, but only writable by the jenkins backup cron job. |
+1 |
2 similar comments
+1 |
+1 |
Been 6 days with no -1s or -0s. I’d like to assert that these can go ahead and be created. |
@bnb agreed. Created the repositories. @rvagg, @sam-github what teams should we give access to the repo? I'm thinking maybe build for jenkins-config-test and build-infra for jenkins-config-release as a start? We also need to likely add some user so that the automation can push the updates. What do we need to add for that? |
I added @nodejs/jenkins-admins to nodejs/jenkins-config-test and @nodejs/jenkins-release-admins to nodejs/jenkins-config-release. Those are the groups that can already see the respective jenkins config right now, so it doesn't expose anything new. @rvagg is in both, so he can add any other groups he deems reasonable. |
The build WG would like to get the ok to add 2 new repositories that we'll use to keep a history of the configuration of the jobs within jenkins.
The repos we want to create are:
More details on the plans are in: nodejs/build#2133
The text was updated successfully, but these errors were encountered: