I'm trying to connect to a repository tfs a written project with xcode 5.
I'm using git-tf and it seems that the configuration in xcode 5 is correct.
The problem that feedback occurs when authentication with the TFS repository.
In xcode 5 open preferences and go in the accounts. I enter the login information with the url and in response I Access denied credentials are incorrect.
What am I doing wrong?
I was encountering the same issues when trying to authenticate in Xcode 5.
Make sure that you enabled Basic Authentication for your user profile for the TFS user account and that you selected "New Team project + GIT" instead of "New Team Project".
You can also try to clone the repository by using Terminal. Type the following command into Terminal and replace XXXXX with your values.
git clone https://XXXXX.visualstudio.com/DefaultCollection/_git/XXXXX
Then provide your credentials. Terminal will now clone the repository when authentication succeeds and your credentials will be saved to your keychain. Now when you try to authenticate in Xcode it will use the saved keychain credentials and it will (probably) successfully add your TFS repository to Xcode.
I hope this will help you!
See:
http://tfs.visualstudio.com/en-us/learn/use-git-and-xcode-with-tfs.aspx
for more information
https://www.visualstudio.com/en-us/get-started/share-your-xcode-projects-vs
Share your Xcode projects in Visual Studio Online using a Git repository. Or, if your team project uses TFVC instead of Git, you can use the git-tf command line tool to check your files into Visual Studio Online.
Enable alternate credentials
You can’t sign in to Xcode with an account that contains an # character, so you’ll have to enable alternate credentials.
Related
I'm using Git with WebStorm's version control already, but have to use TFS version control. After some research fond this plugin but there is no tutorial that aiming to configure that plugin.
Can anyone guide me?
You can opt for using git tfs, locally you can still use Git and all of the advantages you're used to. And then push from git to TFVC. You'll need to install Team Explorer or the Team Explorer Cross Platform Commandline Tools.
Or you can use the native plugin for, thelatest version of the TFS / Azure DevOps (Server) plugin can be found on the Jetbrains site. It requires TFS 2015 or newer. You can use the plugin you found for older versions of TFS.
A good explanation to get started can be found here. The part to configure TFVC is replicated below.
Visual Studio Team Services plugin and TFVC
Before starting with TFVC, we need an external tool. The tool in question is TF command line tool. It ships with the Microsoft Team Explorer Everywhere 2015 and you can download it here.
The file we are interested in is TEE-CLC-14.0.3.zip. Download it and unzip it in a folder of your choice. You should end up with something similar to this.
Now, open the command prompt, move into the folder where you have extracted the TF command line tool and run the following:
tf eula /accept
If command succeeded and you haven’t received any error, you are good to go.
Now back to IDEA. Open the settings panel.
and move to Version Control -> TFVC pane. In the select path to executable field, enter the exact path to the tf.cmd command file located in TF command line tool folder.
Once done, press the test button and you should see the following message
Confirm all of the open windows and get back to the IDEA welcome page. Now you are ready to choose Team Services TFVC (Preview) version control.
At this point, same as for Git, you will be prompted about the connection towards your TFS. The following dialog will be shown.
Move to the Team Foundation Server tab and specify the address of your TFS server, then click connect. You will now be prompted for the credentials and if everything is ok, you will be shown the list of available TFVC repositories.
You can now create a new workspace directly from IDEA and start working with your TFVC repositories.
I am trying to set up TFS for vscode. I am getting the error, unable to validate the collection assuming 'default collection', when signing in. Any recommendations oh how to resolve this issue.
Firstly make sure you have correctly set the TFVC support.
Below is a short list of steps to get up-and-running with TFVC support:
Install the Team Services extension for Visual Studio Code.
Team Foundation Server requires your domain credentials.
Ensure you have a TF command line client installed (either TF.exe or
the TEE CLC).
Set the tfvc.location VS Code setting to the full path of your TF
command line client.
Open a folder containing a Local TFVC Workspace and sign in when
prompted.
Set the SCM Provider to TFVC.
For more detail tutorial you could also take a look at my reply in this question How can I connect to on-premises TFS using visual studio code?
Back on the error message, it may related to the workspace. Check if you have correctly mapped the workspace. Just try to remap the existing workspace or create a new workspace and map sources to a new local folder, then check that again.
Also just try to specify the collection and team project name in the user settings like this:
{
"tfvc.location": "C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\Common7\\IDE\\tf.exe",
"team.remoteUrl": "http://server:8080/tfs/collection",
"team.teamProject": "TeamProjectName",
"tfvc.restrictWorkspace": true,
"window.zoomLevel": 2
}
I'm trying to run UWP build using Team Foundation Server and App Center and it gives me this error.
##[error]C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(3090,5): Error MSB3325: Cannot import the following key file: AppCenterTest.UWP_TemporaryKey.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_480BF88F6934FA8C
I tried creating a private agent for Team Foundation Server which fixed the issue for Team Foundation Server only since the certificate is installed on my private agent. But for App Center by default is running a hosted agent.
How to resolve this issue? Thanks.
Instead of Creating a test certificate in Package.appxmanifest > Packaging > Choose Certificate. I create the certificate in my UWP project Properties > Signing > Choose a strong name key file: > New. This steps resolved my issue.
Take a look at below statement:
Select the right type of build agent
Choose the type of build agent that you want VSTS to use when it
executes the build process. A hosted build agent is deployed with the
most common tools and sdks, and it will work for most scenarios, see
the Software on the hosted build server article. However, you can
create a custom build agent if you need more control over the build
steps. You can use the following table to help you make that decision.
Note: If you plan to target the Windows Anniversary Update SDK (Build 14393) you will need to set up your custom build agent, since the hosted build pool only supports SDK 10586 and 10240. More information to choose a UWP version
Besides, if you use a Git repository, add the certificate file of your project to the repository so that the build agent can sign the appx package. If you don’t do this, the Git repository will ignore the certificate file. To add the certificate file to your repository, right-click the certificate file in Solution Explorer, and then in the shortcut menu, choose the Add Ignored File to Source Control command.
More details please refer this tutorial: Set up automated builds for your UWP app
Trying to push Xcode project to TFS (Git repository), i created local repository for my project in Xcode, then install Git Credential Manager from GitHub, then trying to connect repository from Xcode by adding remote or connect to git repository, but the error message is "Authentication failed because the authentication credentials were rejected."
Would you please provide me with the correct steps.
Knowing that TFS 2015 & Xcode 8.2
The easiest solution for me was to just add your local repository with command line.
git remote add origin ADRESSOFREPO
Afterwards you can use the version control in Xcode to push and pull
TFS 2017 offers you SSH access. The earlier versions, like 2015, requires to setup SSL and Basic Authentication on the server. I guess that this is not properly configured for you.
The steps to setup SSL are described in details in the docs.
Here you can find what is required to configure Basic Authentication.
A couple of caveats:
username should be entered in domain\user format
do not enable Basic Authentication on the default non-SSL site
Has anyone successfully set up VSO & Jenkins & TFS?
Server URL: https://<myproject>.visualstudio.com/DefaultCollection
Login name and user password (using alternative credentials)
What domain name did you use? <domain>\username
If I run the tf command in Command Prompt, it succeeds, but Jenkins shows the same command as failing. I'm lost as to how to debug this. I also tried setting cached credentials for TFS, and not caching them. It seems as though Jenkins does not have cached credentials, but my command prompt does? Why would my system have stored credentials for me, but not Jenkins?
Error from Jenkins: TF30063: You are not authorized to access https://windwardstudios.visualstudio.com/DefaultCollection
With the release of version 4.0.0 of the Jenkins Team Foundation Server plugin, Team Foundation Version Control (TFVC) from Visual Studio Online (VSO) is now officially supported and both Personal Access Tokens (PAT) & alternate credentials can be used.
See the section User name and password in the wiki page.
This is an answer, but may not be what you want to hear. This used to work for us about a year ago. It required someone to stay logged into VisualStudio.com with his MSDN credentials on the build server. Then we simply didn't use credentials in the Jenkins TFS plug-in. Then one day, that simply stopped working. We tried alternative credentials, as #MrHinsh suggested, but never got it to work. Eventually we gave up and switched all of our TFS repositories to git (but still hosted on VisualStudio.com). That does work with the alternate credentials, and we have been very pleased since.
You need to configure Jenkins yo use the alternate credentials. It will not work with any other configuration and the credentials are never stored. Every command that you pass must include the same creds.