Skip to content
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

[JEP-230] Proactively block instance-identity 3.1 #594

Merged
merged 1 commit into from
May 19, 2022

Conversation

jglick
Copy link
Contributor

@jglick jglick commented May 19, 2022

Want to be able to release jenkinsci/instance-identity-plugin#22 without it appearing on the UC, at least for now. Same as in #487.

(I am not sure I have permission to release by the way? Says @core but I am not sure if I am in that group or not. How would I check? Recently I have been using JEP-229 exclusively for releases, which I could do here but it would be tricky since I need to predict the version number in advance.)

@timja

@daniel-beck
Copy link
Contributor

daniel-beck commented May 19, 2022

(I am not sure I have permission to release by the way? Says @core but I am not sure if I am in that group or not. How would I check?

Team definitions are in https://github.com/jenkins-infra/repository-permissions-updater/tree/master/teams

For all actually published plugins, their page on plugins.jenkins.io lists maintainers in the sidebar (usually a few hours out of date at most), we're no longer using the pom.xml for that information.

@daniel-beck daniel-beck merged commit 13aa7b8 into jenkins-infra:master May 19, 2022
@jglick jglick deleted the patch-2 branch May 19, 2022 14:46
@timja
Copy link
Member

timja commented May 19, 2022

It's a list of all active core maintainers basically, but any core maintainer can PR to be in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants