Merge pull request #3006 from native-api/xcode_12.4

Add xcode 12.4

Author: nrios14

_data/snippets.yml

@@ -20,7 +20,7 @@ ghlimit: |
   > If your API or cron triggered builds run on the *same commit
   > or branch* over and over again, you will notice GitHub has a limit of
   > [1000 status updates](https://developer.github.com/v3/repos/statuses/#create-a-status)
-  > *per commit*, which causes the Travis CI build status to display incorrectly 
+  > *per commit*, which causes the Travis CI build status to display incorrectly
   > on GitHub.
   > Avoid this problem by specifying a regularly updated branch for your automated builds.
 all_note: |
@@ -76,33 +76,33 @@ environment_variables: |
   - differ per repository.
   - contain sensitive data, such as third-party credentials.
 contact_enterprise_support: |
-  To get in touch with us, please write a message to 
-  [[email protected]](mailto:[email protected]). If possible, 
+  To get in touch with us, please write a message to
+  [[email protected]](mailto:[email protected]). If possible,
   please include as much of the following as you can:
-   
+
   - Description of the problem - what are you observing?
   - Which steps did you try already?
   - A support bundle (see table below on how to obtain it)
   - Log files from all workers (They can be found at `/var/log/upstart/travis-worker.log` - please include as many as you can retrieve).
   - If a build failed or errored, a text file of the build log
 
   |   TCI Enterprise version | Support bundle |
-  | :---                     | :---           | 
-  | **3.x**                  | Run `kubectl kots admin-console -n [namespace]` to access admin console on `http://localhost:8800`<br />Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at: `http://localhost:8800/app/tci-enterprise-kots/troubleshoot`<br /><br />A command for generating support bundle will appear after selecting: <br />`If you'd prefer, [click here]() to get a command to manually generate a support bundle.` | 
-  | **2.x+**                 | You can get it from `https://<your-travis-ci-enterprise-domain>:8800/support` |  
-
-  Have you made any customizations to your setup? While we may be able to see some 
-  information (such as hostname, IaaS provider, and license expiration), there 
-  are many other things we cannot see which could lead to something not working. 
-  Therefore, we would like to ask you to also answer the questions below in your 
+  | :---                     | :---           |
+  | **3.x**                  | Run `kubectl kots admin-console -n [namespace]` to access admin console on `http://localhost:8800`<br />Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at: `http://localhost:8800/app/tci-enterprise-kots/troubleshoot`<br /><br />A command for generating support bundle will appear after selecting: <br />`If you'd prefer, [click here]() to get a command to manually generate a support bundle.` |
+  | **2.x+**                 | You can get it from `https://<your-travis-ci-enterprise-domain>:8800/support` |
+
+  Have you made any customizations to your setup? While we may be able to see some
+  information (such as hostname, IaaS provider, and license expiration), there
+  are many other things we cannot see which could lead to something not working.
+  Therefore, we would like to ask you to also answer the questions below in your
   support request (if applicable):
-  
+
   - How many machines are you using / what is your Kubernetes cluster setup?
   - Do you use configuration management tools (Chef, Puppet)?
   - Which other services do interface with Travis CI Enterprise?
   - Which Version Control system (VCS) do you use together with Travis CI Enterprise (e.g. github.com, GitHub Enterprise, or BitBucket Cloud)?
   - If you are using GitHub Enterprise, which version of it?
-  
+
   We are looking forward to helping!
 enterprise_2_encryption_key_backup: |
   To make a backup of encryption keys in TCIE 2.x, please follow these steps:
@@ -114,29 +114,29 @@ enterprise_2_encryption_key_backup: |
 enterprise_3_encryption_key_backup: |
   To make a backup of encryption keys in TCIE 3.x, please follow these steps:
 
-  1. Make sure you have appropriate access to the kubernetes cluster: you need credentials for `kubectl` and connection to [travis-api-pod] 
-  2. Run `kubectl exec -it [travis-api-pod] cat /app/config/travis.yml |grep -A 2 encryption` (using Travis API pod is recommended). 
+  1. Make sure you have appropriate access to the kubernetes cluster: you need credentials for `kubectl` and connection to [travis-api-pod]
+  2. Run `kubectl exec -it [travis-api-pod] cat /app/config/travis.yml |grep -A 2 encryption` (using Travis API pod is recommended).
   3. Create a backup of the value returned by that command by either writing it down on a piece of paper or storing it on a different computer.
-github_oauth_access_rights: | 
+github_oauth_access_rights: |
   When you sign in to [travis-ci.com](https://travis-ci.com) using GitHub for the first time, you will receive a message from GitHub saying:
-  
+
   > Travis CI by travis-pro wants to access your [account name] account.
-  
-  and in the repositories section it will state: 
-  
+
+  and in the repositories section it will state:
+
   > This application will be able to read and write all public and private repository data.
-  
-  This is not how Travis CI accesses your data, however we can explain it later in the process. 
-  
+
+  This is not how Travis CI accesses your data, however we can explain it later in the process.
+
   The warning is triggerred due to GitHub OAuth App permissions which Travis CI uses, and due to the available granularity of permission scopes (see GitHub [Scopes for OAuth Apps documentation](https://docs.github.com/en/developers/apps/scopes-for-oauth-apps) ).
-  
-  **Travis CI does not access all your repositories by default**. 
-  
+
+  **Travis CI does not access all your repositories by default**.
+
   Once you acknowledge the access rights, you will see Travis CI OAuth application present in your GitHub [Authorized OAuth Apps list](https://github.com/settings/applications), however **you need to explicitly configure which repositories Travis CI has access to** within your [travis-ci.com](https://travis-ci.com) account. The configuration is done during the activation of Travis CI for your repositories. You can use either the 'All repositories' option or the 'Only select repositories' option during the activation process.
-  
+
   When the Travis CI activation has completed, you will see the actual Travis CI GitHub Application installed in [Installed GitHub Apps](https://github.com/settings/installations) section.
-  
-  Travis CI uses OAuth permissions in the following way:  
+
+  Travis CI uses OAuth permissions in the following way:
 
   1) Travis CI's system synchronizes certain metadata with GitHub. This metadata is required for proper service functioning. In particular, we sync users, orgs, memberships, repos, permissions and, (optionally) branches. This type of sync happens either once a day by schedule or per the user's request. You can find more information and source code [in this repository](https://github.com/travis-ci/travis-github-sync#syncs)