[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs

[mne...@cloudbees.com (JIRA)]

Title: Message Title

Michael Neale commented on JENKINS-48571   Re: checkout scm fails silently after "Could not determine exact tip revision of <branch>" in logs Leandro Narosky Tristan Lewis Alex Suter Ygor Almeida Sorry for the drawn out things.  For users of JobDSL the solution/work around is to always set an id for the SCM, something like:  source { github { //github id "owner-${project_folder}:repo-${project_name}" This will then correct the behavior. Does this work for you? (similarly for other SCMs) If the jobs were created via some other way, then opening the config and saving it (no change needed) will fix it, and blue ocean has been patched to set the id correctly.    See Sam Gleske's last comment here: https://issues.jenkins-ci.org/browse/JENKINS-46290?focusedCommentId=329162&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-329162 and his fix here: https://github.com/samrocketman/jervis/commit/e4cd6324ff22c3593d7e6feab88dff79e516e14b for an example of a jobDSL using it.  Add Comment   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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.