-
Bug
-
Resolution: Unresolved
-
Major
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
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) |
Labels | New: git2 |
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. |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Workflow | Original: JNJira [ 150184 ] | New: JNJira + In-Review [ 186137 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] |
Summary | Original: prune should be before fetch | New: Initial git fetch ignore prune settings of the job |
Summary | Original: Initial git fetch ignore prune settings of the job | New: Initial git fetch ignore prune settings |
Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |