• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin

      In current release version prune works after fetch. (yeah, I saw this bugfix https://issues.jenkins-ci.org/browse/JENKINS-10348)

      But here the bad situation:
      1) Create "abc" branch in git repo.
      2) Build this branch by Jenkins.
      3) Abandon commit and delete branch.
      4) Create "abc/asd" branch, trying to build it... and we got a problem.

      UPD: my bad, now I see what happens with Prune in refactoring branch. But the problem is still there - Prune executes after fetch, not before it.

          [JENKINS-18834] Initial git fetch ignore prune settings

          Sergey Mylnikov created issue -
          Sergey Mylnikov made changes -
          Description Original: In current release version prune works after fetch. (yeah, I saw this bugfix https://issues.jenkins-ci.org/browse/JENKINS-10348)

          But here the bad situation:
          1) Create "abc" branch in git repo.
          2) Build this branch by Jenkins.
          3) Abandon commit and delete branch.
          4) Create "abc/asd" branch, trying to build it... and we got a problem.


          BTW, can someone explain, why in current refactoring branch "prune" completly removed?
          New: In current release version prune works after fetch. (yeah, I saw this bugfix https://issues.jenkins-ci.org/browse/JENKINS-10348)

          But here the bad situation:
          1) Create "abc" branch in git repo.
          2) Build this branch by Jenkins.
          3) Abandon commit and delete branch.
          4) Create "abc/asd" branch, trying to build it... and we got a problem.


          BTW, can someone explain, why in current refactoring branch "prune" completly removed? (commit sha id: 2f01ec91359468e11653e5d222b4a652cf032f55)
          Mark Waite made changes -
          Labels New: git2
          Sergey Mylnikov made changes -
          Description Original: In current release version prune works after fetch. (yeah, I saw this bugfix https://issues.jenkins-ci.org/browse/JENKINS-10348)

          But here the bad situation:
          1) Create "abc" branch in git repo.
          2) Build this branch by Jenkins.
          3) Abandon commit and delete branch.
          4) Create "abc/asd" branch, trying to build it... and we got a problem.


          BTW, can someone explain, why in current refactoring branch "prune" completly removed? (commit sha id: 2f01ec91359468e11653e5d222b4a652cf032f55)
          New: In current release version prune works after fetch. (yeah, I saw this bugfix https://issues.jenkins-ci.org/browse/JENKINS-10348)

          But here the bad situation:
          1) Create "abc" branch in git repo.
          2) Build this branch by Jenkins.
          3) Abandon commit and delete branch.
          4) Create "abc/asd" branch, trying to build it... and we got a problem.


          UPD: my bad, now I see what happens with Prune in refactoring branch. But the problem is still there - Prune executes after fetch, not before it.
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          packadal made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 150184 ] New: JNJira + In-Review [ 186137 ]
          Nicolas De Loof made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]
          Mark Waite made changes -
          Summary Original: prune should be before fetch New: Initial git fetch ignore prune settings of the job
          Mark Waite made changes -
          Summary Original: Initial git fetch ignore prune settings of the job New: Initial git fetch ignore prune settings
          Mark Waite made changes -
          Status Original: Reopened [ 4 ] New: Open [ 1 ]

            Unassigned Unassigned
            sapone Sergey Mylnikov
            Votes:
            4 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: