Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43220

Setting "Commit in Ancestry" causes errors when there are branches without that commit

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin
    • None

      I set up a  project where I added the "Strategy for choosing what to build" behavior and set "Commit in ancestry" to a given commit.

      Now when Jenkins polls the repo, it mostly finds branches without that commit, and ends up spitting out "ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job." over and over.

      I set this up because the commit in question is in a branch that adds bits needed for Jenkins to do its thing, so other older branches simply cannot be run in Jenkins. Once my branch is merged to master and all the older branches are gone, that won't be needed, but for now this is quite annoying.

       

       

          [JENKINS-43220] Setting "Commit in Ancestry" causes errors when there are branches without that commit

          Mark Waite added a comment -

          I've confirmed that this accurately describes the current behavior of the "commit in ancestry" build chooser. I have acceptance tests in my jenkins-bugs-private repository which shows the issue. No plans currently to work on the issue, since it affects fewer users than the other issues currently being investigated.

          Mark Waite added a comment - I've confirmed that this accurately describes the current behavior of the "commit in ancestry" build chooser. I have acceptance tests in my jenkins-bugs-private repository which shows the issue. No plans currently to work on the issue, since it affects fewer users than the other issues currently being investigated.

            Unassigned Unassigned
            autarch Dave Rolsky
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: