Travis CI
Visualize Travis CI repositories, map Travis CI users to employees, and monitor changes through queries and alerts.
- Installation guide
- Travis CI data model
Installation
For this integration, you will need to create an API Token on Travis CI. This can be found under your Settings > API Authentication in Travis CI.
Configuration in JupiterOne
To install the Travis CI integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Travis CI. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Travis CI account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Your Travis CI Hostname and API Token.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | travisci_account | Account |
CodeRepo | travisci_coderepo | CodeRepo |
User | travisci_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
travisci_account | IS | travisci_user |
travisci_user | CREATED | travisci_coderepo |
travisci_user | USES | travisci_coderepo |