![]() ![]() The proposal is thus by default, enable this flag, so we get expected behavior in that all expected branches are available. Which should resolve this issue, it clones all branches (at depth=). If you want to clone submodules shallowly, also pass -shallow-submodules. single-branch unless -no-single-branch is given to fetch the histories near the tips of allīranches. However, git clone -depth supports an additional argument -no-single-branchĬreate a shallow clone with a history truncated to the specified number of commits. ProposalĪs stated below in #30067 (comment 215829463) not fetching all the branches is expected since we are only going far back X commits. ![]() git : << : *common_parameters image : /gitscm/git:latest before_script : - git config -local user.name "$.0-rc1" git push -follow-tags origin "HEAD" done Actual behaviorĪll remotes are available on the runner, albeit at a shallow depth of the main branch Expected behaviorĮven shallow fetch, should always retrieve all branches, not just the current branch. The work around for now appears to be either add a git fetch to the CI task (ugly) or (according to the documentation) set the depth to 0.gitlab-ci.yml This is related to the fact that the branches could not be reached in the current 'depth'. We can create a scenario where not all remotes have been retrieved. However, if git fetch is set with a low depth parameter. To do so, it uses git branch -list -remote "origin/release/v0/*" | sed -n -r 's|.*origin/release/v0/||p' to obtain the list of 'v0' named branches. How to debug it In this snippet two of the remote branches are not shown: git clone -depth 1 git:///pythonwebkit. Clones a repository into a newly created directory, creates remote-tracking branches for each branch in the cloned repository (visible using git branch. What the CI will do, checkout the current branch (gitlab-runner does this of course by default), and go over a list of available existing architecture branches to update these. In our project, we want to create architecture specific branches from our main release branch. ![]() The default in gitlab is 50, but even this does not guarantee all branches are available. The -depth parameter limits the number of revisions not the number of commits.There is not a clone parameter which limits the amount of commits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |