Same here. We have a Multibranch-Pipeline-Job which is connected to a github repository. If the job is triggered by a change, the issue never occurred.
BUT: Additional to the github trigger, we have a nightly-job configured, which triggers the build of one branch at 02:00AM (to verify if the build-env still works, even if there is a long time without change to the main branch). We experienced the described issue on those nightly triggered builds three times in May and three times in June.
All six failed builds were complaining about `timestamps` as invalid option, and two of those failed builds were additionally complaining about the `timeout` option as invalid option.
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.