Hi all,
Fairly often (~50% of the time), when I push a feature branch up to
GH, my multibranch configuration job will get the notification, poll
GH, then bomb with:
Checking pull request #PR-47
Not mergeable, skipping
Even though the branch is mergable. If I force a build manually, it bombs with:
ERROR: Could not determine exact tip revision of PR-47; falling back
to nondeterministic checkout
<snip>
java.io.IOException: Cannot retrieve Git metadata for the build
at
org.jenkinsci.plugins.github.util.BuildDataHelper.getCommitSHA1(BuildDataHelper.java:34)
at
com.cloudbees.jenkins.GitHubCommitNotifier.updateCommitStatus(GitHubCommitNotifier.java:132)
This happens until I repeatedly force the branch indexing. Eventually
something clicks over, and jenkins is aware of the proper commit.
Now, I've seen JENKINS-34120, but this appears to be different. The
commit is mergeable against master (I'm the only one commiting to
master currently, no rebases of the feature branch, etc..), and
there's no other status tests that would be keeping it from building.
It seems like the actual commit notification is getting scrambled.
Has anyone else seen this?
Cheers,
Andrew
--
--
Andrew Melo
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAJY4aWHmAscJ4gPkMcjuOB9Zbw3za6ro4owMdrTtB31%3DossjZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
