You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: user/billing-overview.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,7 @@ Purchase only the credits you need and use them until you run out. Please see mo
76
76
> If a user/organization on the 2 concurrent jobs Plan executes build with jobs for `os: linux` and `os: freebsd`, it will execute as soon as the concurrency capacity is available for particular build jobs.
77
77
78
78
79
+
79
80
### Subscribe to a Concurrency-based Plan
80
81
81
82
1. Sign in to Travis CI with the [Version Control System of your choice](/user/onboarding/).
@@ -400,7 +401,7 @@ vm:
400
401
```
401
402
{: data-file=".travis.yml"}
402
403
403
-
Instance sizes do not apply to Windows build jobs. Visit our [CI Environment Overview page](/user/reference/overview/#gpu-vm-instance-size) for information on the available GPU VM sizes, operating systems, and CPU architecture.
404
+
Instance sizes do not apply to Windows build jobs. Visit our [CI Environment Overview page](/user/reference/overview/#gpu-vm-instance-size) for information on the available GPU VM sizes, operating systems, and CPU architecture.
Travis CI will stop support for macOS starting March 31st, 2025.
186
-
</p>
187
-
</blockquote>
188
-
189
-
With Mavericks, quite a lot has changed in terms of code signing and the keychain application.
190
-
191
-
Signs of issues can be error messages stating that an identity can't be found and that "User
192
-
interaction is not allowed."
193
-
194
-
The keychain must be marked as the default keychain, must be unlocked explicitly and the build needs to make sure that the keychain isn't locked before the critical point in the build is reached. The following set of commands takes care
195
-
of this:
196
-
197
-
```
198
-
KEY_CHAIN=ios-build.keychain
199
-
security create-keychain -p travis $KEY_CHAIN
200
-
# Make the keychain the default so identities are found
## **Mac**: macOS Sierra (10.12) Code Signing Errors
209
-
210
-
<blockquoteclass="beta">
211
-
<p>
212
-
Travis CI will stop support for macOS starting March 31st, 2025.
213
-
</p>
214
-
</blockquote>
215
-
216
-
With the introduction of macOS Sierra (10.12) on our infrastructure, we've seen build jobs that were hanging at the codesigning step of the build process. Here's some information on how to recognize this issue and fix it.
217
-
218
-
Your build is running on macOS Sierra (10.12), if the `osx_image` in your .travis.yml file is `xcode8.3` or higher. See [the macOS Build Environment documentation](https://docs.travis-ci.com/user/reference/osx/) to know which macOS version is associated with each image.
219
-
220
-
The following lines in your build log possibly indicate an occurrence of this issue:
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
228
-
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
229
-
230
-
The build has been terminated
231
-
```
232
-
233
-
**Example: Embed Pods Frameworks**
234
-
235
-
```
236
-
▸ Running script '[CP] Embed Pods Frameworks'
237
-
238
-
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
239
-
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
240
-
241
-
The build has been terminated
242
-
```
243
-
244
-
To fix this issue, you will need to add the following command **after** you have imported your certificate:
> IMPORTANT: It's mandatory to create a keychain with a password for the command `security set-key-partition-list` to work.
276
-
277
-
### Fastlane
182
+
## Fastlane
278
183
279
184
If you are using [Fastlane](https://fastlane.tools/) to sign your app (e.g. with [Fastlane Match](https://github.com/fastlane/fastlane/tree/master/match)), you will need to do something similar to the following in your `Fastfile`:
280
185
@@ -296,7 +201,7 @@ If you are using [Fastlane](https://fastlane.tools/) to sign your app (e.g. with
296
201
)
297
202
```
298
203
299
-
If you are using `import_certificate` directly to import your certificates, it's mandatory to pass your keychain's password as a parameter e.g.
204
+
If you are using `import_certificate` directly to import your certificates, it's mandatory to pass your keychain's password as a parameter, e.g.
300
205
301
206
```
302
207
keychain_name = "ios-build.keychain"
@@ -322,53 +227,6 @@ import_certificate(
322
227
You can also have more details in [this GitHub issue](https://github.com/travis-ci/travis-ci/issues/6791) starting at [this comment](https://github.com/travis-ci/travis-ci/issues/6791#issuecomment-261071904).
323
228
324
229
325
-
## **Mac**: Errors running CocoaPods
326
-
327
-
<blockquoteclass="beta">
328
-
<p>
329
-
Travis CI will stop support for macOS starting March 31st, 2025.
330
-
</p>
331
-
</blockquote>
332
-
333
-
CocoaPods usage can currently fail for a few reasons.
334
-
335
-
### Newer version of CocoaPods required
336
-
337
-
Most Pods now require CocoaPods 0.32.1, but we still have 0.21 preinstalled. If
338
-
you're seeing this error, add this to your `.travis.yml`:
339
-
340
-
```yaml
341
-
before_install:
342
-
- gem install cocoapods -v '0.32.1'
343
-
```
344
-
{: data-file=".travis.yml"}
345
-
346
-
### CocoaPods cannot be found
347
-
348
-
CocoaPods isn't currently installed on all available Rubies, which unfortunately
349
-
means it will fail when using the default Ruby, which is 2.0.0.
350
-
351
-
To work around this issue, you can either install CocoaPods manually as shown
352
-
above, or you can switch to Ruby 1.9.3 in your `.travis.yml`, which should work
353
-
without any issues:
354
-
355
-
```yaml
356
-
rvm: 1.9.3
357
-
```
358
-
{: data-file=".travis.yml"}
359
-
360
-
### CocoaPods fails with a segmentation fault
361
-
362
-
On Ruby 2.0.0, CocoaPods has been seen crashing with a segmentation fault.
363
-
364
-
You can work around the issue by using Ruby 1.9.3, which hasn't shown these
365
-
issues. Add this to your `.travis.yml`:
366
-
367
-
```yaml
368
-
rvm: 1.9.3
369
-
```
370
-
{: data-file=".travis.yml"}
371
-
372
230
## **System**: Required language pack not installed
373
231
374
232
The Travis CI build environments currently have only the en_US language pack
Copy file name to clipboardExpand all lines: user/coverity-scan.md
-9Lines changed: 0 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -22,15 +22,6 @@ See more details about Coverity Scan in the [FAQ](https://scan.coverity.com/faq)
22
22
23
23
It's probably overkill to run static analysis on each and every commit of your project. To increase the availability of the free service to more projects, the addon is designed by default to run analysis on a per-branch basis. We recommend you create a branch named `coverity_scan`, which you can merge into whenever you would like to trigger analysis. See the [FAQ](https://scan.coverity.com/faq#frequency) for information about build submission frequency.
24
24
25
-
## macOS support
26
-
27
-
<blockquoteclass="beta">
28
-
<p>
29
-
Travis CI will stop support for macOS starting March 31st, 2025.
30
-
</p>
31
-
</blockquote>
32
-
33
-
The Coverity Scan addon doesn't work on macOS versions with the SIP feature enabled i.e. on macOS El Capitan (10.11) and higher. Specifically on Travis CI, it currently only works on our Xcode 6.4 image (i.e. with `osx_image: xcode6.4`). However, it's possible to make it work with custom scripts or commands. Please reach out to [support@travis-ci.com](mailto:support@travis-ci.com) to learn how.
0 commit comments