Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
TFS 2017 | TFS 2015
Use this task to run CocoaPods pod install.
CocoaPods is the dependency manager for Swift and Objective-C Cocoa projects. This task optionally runs pod repo update and then runs pod install.
Demands
None
Arguments
| Argument | Description | 
|---|---|
| cwdWorking directory | (Optional) Specify the working directory in which to execute this task. If left empty, the repository directory will be used. Argument alias: workingDirectory | 
| forceRepoUpdateForce repo update | (Required) Selecting this option will force running 'pod repo update' before install. Default value: false | 
| projectDirectoryProject directory | (Optional) Optionally specify the path to the root of the project directory. If left empty, the project specified in the Podfile will be used. If no project is specified, then a search for an Xcode project will be made. If more than one Xcode project is found, an error will occur. | 
Open source
This task is open source on GitHub. Feedback and contributions are welcome.
FAQ
What other kinds of apps can I build?
Build and deploy your app examples
What other kinds of build tasks are available?
Build and release tasks catalog
How do we protect our codebase from build breaks?
- Git: Improve code quality with branch policies with an option to require that code builds before it can be merged to a branch. For GitHub repositories, similar policies are available in GitHub's repository settings under Branches. 
- TFVC: Use gated check-in. 
How do I modify other parts of my build pipeline?
- Build and release tasks to run tests, scripts, and a wide range of other processes. 
- Specify build options such as specifying how completed builds are named, building multiple configurations, creating work items on failure. 
- Supported source repositories to pick the source of the build and modify options such as how the agent workspace is cleaned. 
- Set build triggers to modify how your CI builds run and to specify scheduled builds. 
- Specify build retention policies to automatically delete old builds. 
I selected parallel multi-configuration, but only one build is running at a time.
If you're using Azure Pipelines, you might need more parallel jobs. See Parallel jobs in Azure Pipelines.
How do I see what has changed in my build pipeline?
View the change history of your build pipeline
Do I need an agent?
You need at least one agent to run your build or release.
I'm having problems. How can I troubleshoot them?
See Troubleshoot Build and Release.
I can't select a default agent pool and I can't queue my build or release. How do I fix this?
See Agent pools.
My NuGet push task is failing with the following error: "Error: unable to get local issuer certificate". How can I fix this?
This can be fixed by adding a trusted root certificate. You can either add the NODE_EXTRA_CA_CERTS=file environment variable to your build agent, or you can add the NODE.EXTRA.CA.CERTS=file task variable in your pipeline. See Node.js documentation for more details about this variable. See Set variables in a pipeline for instructions on setting a variable in your pipeline.
I use TFS on-premises and I don't see some of these features. Why not?
Some of these features are available only on Azure Pipelines and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.