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
When you sign in to Travis CI for the first time, we ask for permissions to access
8
+
When you sign in to Travis CI for the first time, we ask permission to access
9
9
some of your data on Assembla. Read the
10
10
[Scopes for the Assembla REST API](https://api-docs.assembla.cc/)
11
11
for general information about this, or pick an explanation of what data we need and why we need it.
@@ -25,33 +25,60 @@ We use scoped OAuth tokens to integrate with Assembla.
25
25
## Used Scopes
26
26
27
27
### repository
28
-
Gives the app read access to all the repositories the authorizing user has access to.
28
+
It gives the app read access to all the repositories the authorizing user has access to.
29
29
> This scope does not give access to a repository's pull requests.
30
30
31
31
### repository:admin
32
-
Gives the app admin access to all the repositories the authorizing user has access to. This permission is needed to add the access key. Travis CI uses the key to read the travis.yml file content.
32
+
It gives the app admin access to all the repositories the authorizing user has access to. This permission is needed to add the access key. Travis CI uses the key to read the travis.yml file content.
33
33
34
34
35
35
### pullrequest
36
-
Gives the app read access to pull requests and collaborate on them. This scope implies repository, giving read access to the pull request's destination repository.
36
+
It gives the app read access to pull requests and collaborate on them. This scope implies a repository giving read access to the pull request's destination repository.
37
37
38
38
### email
39
-
Ability to see the user's primary email address. This should make it easier to use Assembla as a login provider to apps or external applications.
39
+
The ability to see the user's primary email address. This should make using Assembla as a login provider to apps or external applications easier.
40
40
41
41
### account
42
-
Ability to see all the user's account information. Note that this does not include any ability to mutate any of the data.
42
+
The ability to see all the user's account information. Note that this does not include any ability to mutate the data.
43
43
44
44
### team
45
-
The ability to find out what teams the current user is part of. This is covered by the teams endpoint.
45
+
The ability to find out what teams the current user is part of. The teams' endpoint covers this.
46
46
47
47
### webhook
48
-
Gives access to webhooks. This scope is required for any webhookrelated operation.
48
+
Gives access to webhooks. This scope is required for any webhook-related operation.
49
49
50
-
This scope gives read access to existing webhook subscriptions on all resources you can access, without needing further scopes.
51
-
This means that a client can list all existing webhook subscriptions on repository foo/bar (assuming the principal user has access
52
-
to this repo). The additional repository scope is not required for this.
50
+
This scope gives read access to existing webhook subscriptions on all resources you can access without needing further scopes.
51
+
This means a client can list all existing webhook subscriptions on repository foo/bar (assuming the principal user can access
52
+
this repo). The additional repository scope is not required for this.
53
53
54
54
Likewise, existing webhook subscriptions for a repo's issue tracker can be retrieved without holding the issue scope.
55
55
All that is required is the webhook scope.
56
56
57
57
However, to create a webhook for issue:created, the client will need to have both the webhook as well as issue scope.
58
+
59
+
## Version Control System Specific Information
60
+
61
+
Aside from Git Repository integration, Travis CI supports the following VCS (Version Control System) integrations with Assembla:
62
+
63
+
| Repository type | Supported integration | Authorization engine |
Copy file name to clipboardExpand all lines: user/billing-overview.md
+40-7Lines changed: 40 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,8 @@ The variety of plans provides you with the flexibility to choose the plan that s
17
17
18
18
| Billing Period | Concurrency based | Usage-based |
19
19
|:------- |:-----------------:|:-----------:|
20
-
|Month | Concurrent jobs limit<br />Unlimited build minutes on Linux, Windows, and FreeBSD<br />Paid macOS builds (credits)<br /><br />| Very high concurrency limit<br />Paid macOS, Linux, Windows, and FreeBSD build minutes (credits)<br />Paid user licenses (only per users triggering the builds)<br /><br /> |
21
-
|Annual |Only grandfathered | Very high concurrency limit<br />Paid macOS, Linux, Windows, and FreeBSD build minutes (credits)<br />Paid user licenses (only per users triggering the builds)<br /><br />Purchase in Travis CI or contact support [for plans over $3,300](https://app.travis-ci.com/account/plan) in Travis CI|
20
+
|Month | Concurrent jobs limit<br />Unlimited build minutes on standard vm sized Linux, Windows, and FreeBSD<br />Paid macOS builds (credits)<br />Paid premium VM size (credits). Contact sales for other options.<br /><br />Purchase in [Travis CI](https://app.travis-ci.com/account/plan). | Very high concurrency limit<br />Paid macOS, Linux, Windows, and FreeBSD build minutes (credits)<br />Paid user licenses (only per users triggering the builds)<br /><br />Grandfathered only.|
21
+
|Annual |Available, same build rules as monthly. Purchase in [Travis CI](https://app.travis-ci.com/account/plan) or contact support. | Very high concurrency limit<br />Paid macOS, Linux, Windows, and FreeBSD build minutes (credits)<br />Paid user licenses (only per users triggering the builds)<br /><br />Contact support for high volume annual usage-based plans.|
22
22
23
23
24
24
For most of users, a single concurrency-based plan should be sufficient. However, if you build a lot of minutes per month and concurrency becomes a bottleneck, please contact Travis CI asking for a Usage-based plan.
@@ -63,7 +63,7 @@ Credits are used to pay for each build job minute on macOS. Purchase only the cr
63
63
1. Sign in to Travis CI with the [Version Control System of your choice](/user/tutorial/).
64
64
2. Navigate to the [Plan tab](https://app.travis-ci.com/account/plan) and select 'X concurrent jobs Plan'.
65
65
3. Enter your billing details. **Please note that all prices are provided netto, w/o any VAT or other applicable local taxes**. If you are EU based VAT paying company, do not forget to enter your VAT number.
66
-
4. Confirm transaction.
66
+
4. Confirm the transaction.
67
67
68
68
69
69
## Usage-based plans
@@ -262,15 +262,15 @@ With every build started, Travis CI keeps track of how many unique users trigger
262
262
263
263
| Area | Details |
264
264
| :--- | --- |
265
-
| **Payment** | Credits are paid in advance:<BR />1. Upon purchasing a Plan, an immediate charge is applied depending on credits allotment coming with a Plan.<BR />2. The additional credit addons can be purchased at any time, and credits are only used when you need them. The charge is applied immediately upon transaction.<BR /><BR />The user license cost is charged automatically in arrears at the end of each billing period (Usage Plan w/o subscription). The number of unique users triggering a build is charged according to the license rates.<br /><br />The Free Plan assigned upon sign-up grants you unlimited users for free. |
265
+
| **Payment** | Credits are paid in advance:<BR />1. Upon purchasing a Plan, an immediate charge is applied depending on the credits allotment coming with a Plan.<BR />2. The additional credit addons can be purchased at any time, and credits are only used when you need them. The charge is applied immediately upon transaction.<BR /><BR />The user license cost is charged automatically in arrears at the end of each billing period (Usage Plan w/o subscription). The number of unique users triggering a build is charged according to the license rates.<br /><br />The Free Plan assigned upon sign-up grants you unlimited users for free. |
266
266
| **Private/Public repositories** | With Credits, you can build over both private and public repositories. <BR/> With OSS Credits, you can build only over public repositories. |
267
-
| **Build job limits** | Very high. <BR/><BR/>The Free Plan assigned automatically upon sign-up has a limit of 20 concurrent jobs. The paid usagebased plans start from a 40 concurrent jobs limit. |
267
+
| **Build job limits** | Very high. <BR/><BR/>The Free Plan assigned automatically upon sign-up has a limit of 20 concurrent jobs. The paid usage-based plans start from a 40 concurrent jobs limit. |
268
268
269
269
270
270
### Usage-based Plan - How to obtain?
271
271
272
272
1. Sign in to Travis CI with a [Version Control System of your choice](/user/tutorial/).
273
-
2. Navigate to the [Plans](https://app.travis-ci.com/account/plan) and have your billing and contact details fill in correctly.
273
+
2. Navigate to the [Plans](https://app.travis-ci.com/account/plan) and have your billing and contact details filled in correctly.
274
274
3. Contact [Travis CI support](mailto:[email protected]) requesting a Usage-based Plan.
275
275
276
276
@@ -299,7 +299,40 @@ VM size property impacts the cost of build minutes/credits usage in the followin
299
299
300
300
301
301
302
-
> If you run a Linux build in usage model, it'll cost you 10 credits. If you run a Linux build under a concurrency plan, you do not need credits, as the subscription covers the cost. However, if you decide to run a Linux build using the `large` instance size, you will need in both cases 20 credits per every started build minutes (2 x 10 credits).
302
+
> If you run a Linux build in usage model, it'll cost you 10 credits. If you run a Linux build under a concurrency plan, you do not need credits, as the subscription covers the cost. However, if you decide to run a Linux build using the `large` instance size, you will need, in both cases, 20 credits per every started build minutes (2 x 10 credits).
303
+
304
+
305
+
## GPU VM Instance Sizes and Credit Cost for GPU builds
306
+
307
+
Travis CI allows users to trigger GPU builds both in usage-based and concurrency-based plans.
308
+
309
+
GPU builds allow you to choose the instance size the build will run on (for the 'full vm' build job). X-large instance sizes deliver more resources (vCPU and RAM) for your build jobs. This can be done by setting a 'vm' property in the .travis.yml config. This property allows you to choose the Virtual machine instance for a build:
310
+
311
+
```yaml
312
+
vm:
313
+
size: [gpu-medium | gpu-xlarge] #new values in the schema for existing key
314
+
```
315
+
316
+
Instance sizes do not apply to Windows, and OSX build jobs. Visit our [CI Environment Overview page](/user/reference/overview#gpu-vm-instance-size) for information on the available GPU VM sizes, operating system, and CPU architecture.
317
+
318
+
To use instance sizes:
319
+
320
+
* you need to have credits under your account, regardless of the plan (Concurrency or Usage-based) you use.
321
+
* you need to add the tags mentioned above to your `.travis.yml.`
322
+
* you need to select a Linux operating system in your `travis.yml.`
323
+
324
+
GPU VM size property impacts the cost of build minutes/credits usage in the following way:
Copy file name to clipboardExpand all lines: user/build-config-imports.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -231,9 +231,14 @@ import:
231
231
```
232
232
{: data-file=".travis.yml"}
233
233
234
-
This mode first merges your `.travis.yml` contents into the `one.yml` file (overwriting, if required, sections in `one.yml` with content from `.travis.yml`). The results are merged into the `two.yml` file (again, items in the result of the previous merge win over what’s in this one, as the `deep_merge` mode is specified here).
235
-
236
-
The reasoning behind this is that in many cases when you import something to your `.travis.yml’ file, you want to be able to overwrite or customize that imported configuration with config in your `.travis.yml` file.
234
+
This mode first merges your `.travis.yml` contents into the `one.yml` file (overwriting,
235
+
if required, sections in `one.yml` with content from `.travis.yml`). The results are
236
+
merged into the `two.yml` file (again, items in the result of the previous merge win
237
+
over what’s in this one, as the `deep_merge` mode is specified here).
238
+
239
+
The reasoning behind this is that in many cases when you import something to your
240
+
`.travis.yml`file, you want to be able to overwrite or customize that imported
241
+
configuration with config in your `.travis.yml` file.
Copy file name to clipboardExpand all lines: user/common-build-problems.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -630,3 +630,13 @@ This creates only one job, _Peanut Butter and Bread_ under the stage named _Bre
630
630
## **Node**: Script execution before dependency installation causes build failures
631
631
632
632
When adding custom setup instructions to a NodeJS build, add them in the `before_script` phase and not before _dependencies are installed_. The `before_script` phase is the safest place to add custom setup scripts. Symptoms of this problem include previously succeeding builds suddenly failing due to the addition of a new dependency.
633
+
634
+
## **Node**: NPM/YARN throw ***Error: connect ENETUNREACH*** or build hangs in the install phase i.e. `npm install` or `yarn install` for NodeJs versions 16+ on LXD images (ppc64le, arm64 and s390x)
635
+
636
+
This seems to be a known bug and the details can be reviewed at https://github.com/npm/cli/issues/4163. Add the following to resolve the issue:
0 commit comments