Sam Gleske added a comment - 2018-02-18 05:47 I would like to point out that this plugin is attempting to resolve the tip of my "jervis_simple" branch (as it should because I am building the jervis_simple branch) but for some reason is flailing about with the tip of master branch. Started by user Sam Gleske Running in Durability level: MAX_SURVIVABILITY Loading library Jervis Global Library@master Attempting to resolve master from remote references... > git --version # timeout=10 using GIT_ASKPASS to set credentials GitHub user and personal access token used by multibranch pipeline jobs for the GitHub API > git ls-remote -h -t https://github.com/samrocketman/jervis.git # timeout=10 Found match: refs/heads/master revision a82c0668ab31f0c992d26575e415971648c5c185 > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/samrocketman/jervis.git # timeout=10 Fetching without tags Fetching upstream changes from https://github.com/samrocketman/jervis.git > git --version # timeout=10 using GIT_ASKPASS to set credentials GitHub user and personal access token used by multibranch pipeline jobs for the GitHub API > git fetch --no-tags --progress https://github.com/samrocketman/jervis.git +refs/heads/*:refs/remotes/origin/* Checking out Revision a82c0668ab31f0c992d26575e415971648c5c185 (master) > git config core.sparsecheckout # timeout=10 > git checkout -f a82c0668ab31f0c992d26575e415971648c5c185 Commit message: "bump to snapshot" > git rev-list --no-walk a82c0668ab31f0c992d26575e415971648c5c185 # timeout=10 [Pipeline] End of Pipeline ERROR: Could not determine exact tip revision of jervis_simple Finished: FAILURE

Stephen Connolly added a comment - 2018-02-18 07:33 This looks to be the exact situation of the second case I describe in https://issues.jenkins-ci.org/browse/JENKINS-48571?focusedCommentId=329111&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-329111 Namely the Job DSL plugin is being used to configure a branch source that has a null id. You must provide an ID: https://github.com/samrocketman/jervis/blob/b25af324cce229255fd34c9070f32da4d0d8b393/jobs/jenkins_job_multibranch_pipeline.groovy#L38-L52 Change github { //github credentialsId 'github-user-and-token' repoOwner project_folder repository project_name //behaviors not supported by job dsl //additional behaviors traits { headWildcardFilterWithPR { includes "${JERVIS_BRANCH}" excludes '' } } } to github { //github id 'anything-does-not-matter-as-only-one-source-configured' credentialsId 'github-user-and-token' repoOwner project_folder repository project_name //behaviors not supported by job dsl //additional behaviors traits { headWildcardFilterWithPR { includes "${JERVIS_BRANCH}" excludes '' } } } And the problem should go away. Sam Gleske can you confirm the above?

Sam Gleske added a comment - 2018-02-18 20:14 Thanks for the pointer, I will make the change to test.  I'm glad my projects are open source so you are able to inspect it and give me pointers Stephen Connolly .  I will report back my results.

Sam Gleske added a comment - 2018-02-18 20:52 Stephen Connolly your suggestion appears to have fixed the issue. Fixed by https://github.com/samrocketman/jervis/commit/e4cd6324ff22c3593d7e6feab88dff79e516e14b I'll do some more testing but it now appears to work reliably. Required After making the change from Stephen Connolly 's suggestion I had to click "Scan Repository Now".  The problem continued to be broken until I scanned the repository for branches. Results (the fixed flow) The following flow is how I reproduced reliably and confirmed the fix. Bootstrapped Jenkins with vagrant Generated a multibranch pipeline for samrocketman/jervis project. Clicked "Scan repository Now" so branches would be detected. Clicked "Build now" on the jervis_simple branch.  This always succeeded the first time. Log into Jenkins and restart it.  /etc/init.d/jenkins stop; /etc/init.d/jenkins start Visit the jervis job and click "Build now" (the ERROR used to occur here every time with this flow; clicking build repeatedly and restarting Jenkins did not help and caused the same failure every time) After the fix, step 6 above now always works and I no longer encounter the error.  I will test further to be absolutely sure it's fixed.  Thanks Stephen!

Michael Neale added a comment - 2018-02-20 01:00 great - I might close this as a duplicate, but Sam Gleske 's comment above is handy! thanks