|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It worked for me too.
security delete-keychain jenkins-jobName
The problem is that if the build crashes (for any other reason) it removes the jobName and on the next build (Let's say that the other problem was causing the crash has been fixed) 'security delete-keychain jenkins-jobName' tries to remove jobName which has been removed on last build already and therefore it crashes again since it can't find the jobName.
Is there anyway to ensure that jobName does exist before trying to delete it?
Or any other ideas please?