-
Improvement
-
Resolution: Won't Do
-
Trivial
There is no option to fetch and prune tags on all submodules in Jenkins.
In our environment, it happens in rare cases that tags are force-pushed on the main repo and on submodules. We did not find any way to reflect the actual tags before build using Jenkins, except with a full repository wipeout.
Also we have a case where a new tag on the submodule repository was not present on our builder at build time.
We tried using a command such as git fetch --prune origin "refs/tags/:refs/tags/ in the build steps, but this fails as the credentials cannot be used at that stage.
[JENKINS-71132] Git plugin: fetch and prune tags on submodules
Summary | Original: Git plugin: prune tags on submodules | New: Git plugin: fetch and prune tags on submodules |
Description |
Original:
There is no option to fetch and prune tags on all submodules in Jenkins.
In our environment, it happens in rare cases that tags are force-pushed on the main repo and on submodules. We did not find any way to reflect the actual tags before build using Jenkins, except with a full repository wipeout. We tried using a command such as {{git fetch --prune origin "refs/tags/*:refs/tags/*}} in the build steps, but this fails as the credentials cannot be used at that stage. |
New:
There is no option to fetch and prune tags on all submodules in Jenkins.
In our environment, it happens in rare cases that tags are force-pushed on the main repo and on submodules. We did not find any way to reflect the actual tags before build using Jenkins, except with a full repository wipeout. Also we have a case where a new tag on the submodule repository was not present on our builder at build time. We tried using a command such as {{git fetch --prune origin "refs/tags/{*}:refs/tags/{*}}} in the build steps, but this fails as the credentials cannot be used at that stage. |
Assignee | Original: Mark Waite [ markewaite ] |
Resolution | New: Won't Do [ 10001 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |