-
Bug
-
Resolution: Unresolved
-
Major
-
None
git fetch has three options to fetch tags:
- "git fetch" fetches a branch with tags reachable, the ideal default
- "git fetch --no-tags" fetches a branch without tags
- "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also
in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the clone size.
this should be for multibranch pipeline, not sure what the correct component is.
the current workaround is:
// code placeholder
[JENKINS-56517] fetch has 3 options: nothing, --no-tags, --tags, jenkins only 2
Description |
Original:
"git fetch" fetches a branch with tags reachable, the ideal default "git fetch --no-tags" fetches a branch without tags "git fetch --tags" fetches tags not reachable from the branch in jenkins variang 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? set to blocker as otherwise nobody seems to read tickets :( |
New:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch in jenkins variang 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? this should be for multibranch pipeline, not sure what the correct component is. set to blocker as otherwise nobody seems to read tickets :( |
Description |
Original:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch in jenkins variang 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? this should be for multibranch pipeline, not sure what the correct component is. set to blocker as otherwise nobody seems to read tickets :( |
New:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variang 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? this should be for multibranch pipeline, not sure what the correct component is. set to blocker as otherwise nobody seems to read tickets :( |
Description |
Original:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variang 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? this should be for multibranch pipeline, not sure what the correct component is. set to blocker as otherwise nobody seems to read tickets :( |
New:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? this should be for multibranch pipeline, not sure what the correct component is. set to blocker as otherwise nobody seems to read tickets :( |
Priority | Original: Blocker [ 1 ] | New: Major [ 3 ] |
Component/s | New: multi-branch-project-plugin (not Pipeline) [ 21127 ] |
Component/s | New: pipeline [ 21692 ] |
Description |
Original:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? this should be for multibranch pipeline, not sure what the correct component is. set to blocker as otherwise nobody seems to read tickets :( |
New:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the checkout size. this should be for multibranch pipeline, not sure what the correct component is. |
Description |
Original:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the checkout size. this should be for multibranch pipeline, not sure what the correct component is. |
New:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the clone size. this should be for multibranch pipeline, not sure what the correct component is. |
Component/s | New: git-plugin [ 15543 ] | |
Component/s | Original: multi-branch-project-plugin (not Pipeline) [ 21127 ] | |
Component/s | Original: pipeline [ 21692 ] | |
Component/s | Original: scm-api-plugin [ 18054 ] |
Description |
Original:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the clone size. this should be for multibranch pipeline, not sure what the correct component is. |
New:
git fetch has three options to fetch tags: * "git fetch" fetches a branch with tags reachable, the ideal default * "git fetch --no-tags" fetches a branch without tags * "git fetch --tags" fetches tags not reachable from the branch, i.e. other branches also in jenkins variant 1, fetching tags reachable cannot be configured any more (with ease), while it reasonably should be the default? also the branch name is not there in the git repo fetched. all of these operatins add labels to existing commits so do not increase the clone size. this should be for multibranch pipeline, not sure what the correct component is. the current workaround is: {code:java} // code placeholder {code} |