I updated to the latest version yesterday and performed the re-key 
operation twice. First I scheduled the operation for the next startup and 
restarted the service.
Jenkins says the re-key operation was successful, but the log lists several 
files that couldn't be opened or replaced.

I tried again using the option to run in background with the same result. 
Jenkins says the operation was successful but the log lists yet the same 
problems.
I checked the read/write permissions for some of the files listed and 
everything seems fine.

Can I trust Jenkins and consider it done?

Reply via email to