I have to use TFS for my Mac machine for iPhone app development. So that I have used the following step as from the Git-TF_GettingStarted.html
Extract the contents of Git-TF-Release-Preview.zip to a folder on your local machine,
i.e. C:\git-tf on Windows, or /user/git-tf on Mac/Linux. for installation.
But while giving the command "git tf clone http://myserver:8080/tfs $/TeamProjectA/Main "
an error is coming as
git: 'tf' is not a git command.
Then I have removed the tf from the command, at that time it get worked and asked the username and password, but authentication get failed.
How can I resolve this issue?, if anybody has idea then please help me.
You haven't actually set your PATH variable, which is why you're getting the command not found problem.
If you've set your path, using, as an example: PATH=$PATH:$HOME/git-tf-2.0.2.20130214, then the git command will allow the sub-command tf, which should work like the documentation suggests, as in:
git tf clone …
will work once you've set the PATH variable, otherwise you'll have to reference the git-tf command directly.
The command that is extracted is git-tf, and git is smart enough to look for the git-tf command if you have set the PATH and try to use the operation git tf.
You better go with TFS Everywhere http://www.microsoft.com/en-us/download/details.aspx?id=4240
And use Eclipse like a client for your development in XCode.
Related
When I am trying to give the Git URL in Jenkins source code management, I am getting this error:
Failed to connect to repository : Error performing command: git.exe ls-remote -h https://github.com/shivnathr/DevOPS1 HEAD
How can I avoid it?
Make sure your Jenkins is running as your account, and not as a service with a technical account.
That way, Jenkins will benefit from the same configuration as your account.
But first, check if you can, with your account, in a simple CMD shell session, execute that same command successfully:
git.exe ls-remote -h https://github.com/shivnathr/DevOPS1 HEAD
When you configure this in Jenkins, it gives this error. But if you ignore this error, does it then work for the build? Have you configured git tools in Jenkins? I am not sure if having git in the path for the user running Jenkins will work (it might), but if you configure a git tool, it should use the first tool in the list to find git. BUT, if the first tool is set to auto-install, then this problem can occur. Make sure the first git tool is just pointing to an installation on the machine. I believe this is a bug. I found this on one of my installations, but I have yet to open an issue for it.
Not a duplicate of
'git' is not recognized as an internal or external command
I've set up my github repository, downloaded Github Desktop, but I can't figure out how to upload files to the repo.
Here are Github's instructions for me
I've done the "quick set up", and have set up github Desktop on my computer. However, I can't get the command line repo setup to work. Whenever I type out a git command, it gives the above error. I've tried to research why this happens, but the only relevant source (linked above) gave instructions regarding a past version of the github app.
I know this is probably very simple, but I'm quite new and can't find out what to do. Any help is appreciated.
If somehow the GitHub Destop did not add an internal Git to your PATH, you can do so manually with the latest Git for Windows release.
Uncompress the archive PortableGit-2.15.0-64-bit.7z.exe anywhere you want and add it to your PATH (as I do here), then launch GitHub Desktop.
I use git lfs to store the large files of my git repo. I then try to build this repo with hosted agents. My build is pretty simple. It has a single task: Execute PowerShell. In the invoked script, the first thing that I want to do is to fetch my lfs dependencies. I therefore have the following in my script:
& git lfs fetch
Unfortunately, my build fails with the following error:
2016-03-04T19:49:05.7021988Z ##[error]git: 'lfs' is not a git command. See 'git --help'.
2016-03-04T19:49:05.7031986Z ##[error]Did you mean this?
2016-03-04T19:49:05.7041987Z ##[error] flow
Since I can't install anything on hosted agents, how am I supposed to have git lfs available?
EDIT
In this issue, I am not talking about git lfs authentication problems as described here. I am strictly talking about the issue of calling git lfs.
Once you are able to call git lfs, look at this answer to solve the authentication problem.
Git LFS is now supported by default on the Hosted Build Controller. But you do need to enable it in your get sources step.
You get this error message because git-lfs isn't installed on Hosted Build Agent by default.
And since you are using Hosted Build Agent, it would be a little troublesome to install git-lfs via Chocolatey on it as you don't have administrator permission. An alternative way would be download the binary files for git-lfs directly and upload it into Source Control. Then you can invoke the git-tfs.exe with an absolute path in your script.
Here are some more details around the solution provided by Eddie. git lfs is not a built-in command. It is a git custom command.
When you call git lfs, git.exe does not know about the lfs command. So it looks in the PATH environment variable and searches for a program named git-lfs.exe. Once found, it calls that program with the provided argument.
So calling git-lfs.exe pull is equivalent to calling git.exe lfs pull.
The solution suggested is therefore to download git-lfs.exe, add it your git repo (it should obviously not be tracked by LFS), and call git-lfs.exe.
It is also possible to add the folder that contains git-lfs.exe to your path environment variable. This makes it possible to use commands like git.exe lfs pull as you usually do.
If you are allowed to install software and have internet access during build you might be able to install git-lfs using the Chocolatey package in a cmd / PowerShell task prior to your git-lfs operation.
I am new to command line and have no idea how to use. I have Putty command line and would like to connect to my GitHub. Putty asks for a "Hostnamne/IP address". I do not know what to insert so it can work. Could anyone please help me?
PuTTY isn't something that you would use to connect directly to GitHub. It is an SSH client, but you need a Git client. Since GitHub doesn't provide interactive SSH, PuTTY won't be of much use.
I'm going to assume you're on Windows since that's where PuTTY is most often used. You can install the latest official release of Git for Windows, but it's probably worth installing one of the recent 2.x prereleases instead. These will be the official versions very shortly.
Once you have Git installed you should be able to run "Git Bash", which will drop you into a command line. At this point you can use git clone to clone an existing repository, git init to create a brand new one, or any number of other things. You'll probably want to find a tutorial or read a book before going much further.
If you'd prefer a graphical Git client there are many options.
I have been forced to use other apps, and the command line since Github for Windows is not allowing me to commit changes. I would like to understand what's the problem, but I simply get a prompt with this message:
Commit failed
Failed to create new commit
Then, it gives me the option of go to the Git Shell or to cancel. While I am not an expert with the terminal, I am able to make commits when I choose to go to the Git Shell (or to any other application for that matter).
I am using Github 2.0.5 on Windows 7.
After an exchange with the Github for Windows developers, the issue has something to do with Windows inability to work with paths when they're too long. The node_modules folders generated by Node.js is the culprit of this issue in my particular case.
However, the node_modules folders in my repository are gitignored. The fact that even when gitignored they create a problem in Github for Windows means the developers have to address the situation.
I expect a response or a patch from the developers soon. They have been very helpful. In the meantime, I am using SourceTree as my Windows Git GUI.