Ok, we have done more detailed investigation and here are new findings:

  • faulty hash is hash of merge commit created by GitHub automatically from one of older builds (before force push)
  • problem manifests when using build configurations: in global build instance description correct hashes are used, but configuration-specific consoles still try to checkout the old one
  • it is still unclear how to get PR in that state but once it gets there, it is stuck always trying to checkout same hash in configuration
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.

Reply via email to