-
Notifications
You must be signed in to change notification settings - Fork 741
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
SPOF check #321
Comments
I do not have opportunity to properly maintain this repo, sorry |
Ack, I'll find a few more people who are willing to cut a release |
@kohsuke I think the last time I tried it failed when uploading the artifactes. |
@kohsuke This remains an issue. Care to grant me rights? |
It is not enough to have merge rights here. You would also need Maven
Central permissions to deploy it
…On Fri, Oct 11, 2019, 22:50 Liam Newman ***@***.***> wrote:
@kohsuke <https://github.com/kohsuke> This remains an issue. Care to
grant me rights?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#321>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW4RIBTNLA74V4T6BDI7UTQODRKFANCNFSM4CZQF5TA>
.
|
@oleg-nenashev |
Actually they grant it to anyone if the request is approved by the maintainer: https://issues.sonatype.org/browse/OSSRH-13404 @bitwiseman If you create a OSSRH account, I think we can ask for permissions for us both. @lanwen and @KostyaSha maybe also interested as GitHub plugin maintainers in Jenkins |
On my experience they can also grant perms of you are in push access level in github. But that depends on visibility. |
Done. I've been informed that I now have permissions. |
Released v1.99. I'm going to close this. If we need to we can reopen it when SPOF becomes a concern again. |
2 years ago i spent 4 months getting release with fixes. After it @oleg-nenashev got backup access to repo and maven central. Now it seems that story repeats.
@kohsuke please check that somebody else ( @stephenc , @oleg-nenashev ) has ability to do new releases.
The text was updated successfully, but these errors were encountered: