-
Notifications
You must be signed in to change notification settings - Fork 56
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
Jenkins plugin Json or P12 key are not found and saved empty #13
Comments
I have totally the same problem. I've tried to populate *.json and *.p12 files on Jenkins manually but it wasn't help me. |
I have the same issue, is anyone looking into this? |
I have the same issue to, nobody find a bypass ? or a way to put manualy the json file ? ty. |
Version 0.5 doesn't seem to have this issue. Check that the user you are running Jenkins on has permission to change file permissions. I tried on a fresh install of the latest version of Jenkins as well as a slightly older version. Both worked as long as my Jenkins user had sufficient privileges. |
How do I go about checking that? Jenkins is a Windows service and I start the job as an admin user. |
Actually, I'm sorry, 0.6-SNAPSHOT has this fixed. 0.5 still has the issue. It looks like it's mostly ready to deploy. I'm not sure what the holdup is but even getting the snapshot version on maven would be helpful. |
Thank you for the confirmation. Is there a way for us to get the 0.6 version before it's officially released? |
Today, I got the 0.6 version updated announcement.
|
When I try to push a Docker image to GGloud i get this stacktrace
When I open my credentials the file is gone.
Key files are generated but not found. Also the files are empty
Jenkins for Windows ver. 2.73.3
Google OAuth Credentials plugin 0.5
The text was updated successfully, but these errors were encountered: