I should further note two things: First, the aforementioned behavior still holds. If I manually run the couchbase-alpha-cluster-01 job, though it still fails, the git-hook thereafter works. However, if I restart Jenkins, the problem then comes back.

Second, there may be an additional variable or more at play here in that this never-yet-succeeded job has been on this server for a few weeks w/o causing problems. I suppose it is possible that the Jenkins server has never been restarted since the job was created but that seems unlikely in our environment.

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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to