![]() Resolving deltas: 100% (4293/4293), done.Ä®rror: Failure while executing: git clone -depth 1 -branch v0.16. Cellar/git/1.8.4/bin/gitĬloning into '/usr/local/Library/Taps/phinze-cask'. Lrwxr-xr-x 1 jsmitley admin 27 Sep 24 06:49 /usr/local/bin/git ->. It allows you to only fetch files from the. This performs the same action as option one, except that the -single-branch option was introduced in Git version 1.7.10 and later. git clone -b -single-branch Here -b is just an alias for -branch. Git clone -depth 1 -branch v0.16.2 /Users/jsmitley/Library/Caches/Homebrew/brew-cask-git git clone -branch -single-branch or.Like other people have noticed, I can manually run this command without a problem: I guess I run another instruction on the 1st try that changed the git tree and ended up trying to pull everything when I run git pull.I've been having the same problem since yesterday (9/23/13), have never seen before. I tested the above steps again and they were fast. Haven't you perceived some increase in the rebuild time? (or maybe that is not so big compared to the total rebuild time, in most cases) What I normally do in my (non-discourse) projects is to make a new image for every new version, but that may not be feasible to you (considering how you do it currently). Not saying that having the entire repository in the base image is better, but the code in `` will run on every rebuild, even if only a plugin was added or a setting was changed in `app.yml`. You can try running just the above instructions locally and see. When `git pull` is called, **the entire repository is pulled**, and can take several minutes, because only a shallow clone was done before. git clone -depth clone time git clone :ruby/ruby.git 128.44s user 37.45s system 94 cpu 2:55.36 total depth time git clone -depth1 :ruby/ruby.git 1.26s user 1.42s system 20 cpu 12. Git remote set-branches -add origin master To clone a branch without fetching other branches, you can use the git-remote add command with git-fetch. Git remote set-branches -add origin tests-passed Just consider the following instructions: Wouldnât the way itâs doing now have slower rebuilds, even when tests-passed branch is used? Youâre right, at that time we donât know the version, it seems the base image uses the current version + tests-passed branch, although the branch will have the commit at the time in which the image was build. Suitable for the scene of git clone -Depth 1: You just want. Depth is used to specify the cloning depth, which means that only clones are close to the last time. Problem is that at the image build time I donât know what branch you will want in the future. The benefits of using git clone - Depth 1 are to limit the depth of Clone, and will not download the history of git collaboration, which can greatly accelerate the speed of clones. HEAD is now at d6121249d3 Version bump to v2.6.0 If you want to create a new branch to retain commits you create, you mayÄo so (now or later) by using -b with the checkout command again. ![]() State without impacting any branches by performing another checkout. You can look around, make experimentalĬhanges and commit them, and you can discard any commits you make in this I, INFO - : > cd /var/Note: checking out 'v2.6.0'. Instead of the expected output when using the commit just before that one. I, INFO - : > cd /var/error: pathspec 'v2.6.0' did not match any file(s) known to git The problem shows like this when specifying version: v2.6.0 when using e2eb085714dfcf2aa0117b0f2fdf39b762b0e18d I, INFO - : > cd /var/I, INFO - : This is useful to install older versions of discourse, for test purposes. A recent commit in docker_discourse breaks the ability to specify a tag (for instance v2.6.0) in the version: value of app.yml.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |