As an alternative, you can consider
https://www.jenkins.io/doc/developer/publishing/releasing-cd/ which does
not require you to have any credentials beyond GitHub write access to the
plugin.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
Thanks Gavin! That's my fault for not resetting the password on time.
Oh well, and that log4jshell one messed up a lot of things for us today,
too.
I hope the investigation goes well, it seems that JREs should default
trustURLCodebase to false everywhere.
Thanks for the info, as always!
Thanks,
security team has taken down accounts.jenkins.io and
beta.accounts.jenkins.io as they are java apps until they have a chance to
look at the log4j exploit in them.
As for your password, it was reset early September because of the
confluence hack -
Hi folks,
I'm afraid there's something wrong with my account and I need your help.
We have a plugin release scheduled for today, but when I tried doing the
regular "mvn release:prepare release:perform", it showed "[ERROR] Failed to
execute goal org.apache.maven.plugins:maven-deploy-plugin ...
