Skip to content

Start building

Integration · Developer

AI agents for Travis CI

Check builds on Travis CI (travis-ci.com): list repositories and their builds, read a build's jobs and a job's log, start a build on a branch, and restart or cancel builds and jobs, with a Travis CI API token.

Actions
10
Read
6
Write
4

Actions

What your agents can do in Travis CI

10 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 6

Look things up. Nothing changes.

  • List repositories

    Lists the repositories the token's user can see on Travis CI, 25 at a time by default.

  • Get a repository

    Reads one repository by its slug (owner/name, for GitHub repositories) or numeric ID.

  • List a repository's builds

    Lists a repository's builds, newest first, optionally only one branch, state (created, received, started, passed, failed, errored, canceled) or trigger (push, pull_request, api, cron).

  • Get a build

    Reads one build by ID: its state, number, duration, started_at and finished_at, branch, commit, repository, stages, and its jobs (each job's ID and state).

  • List a build's jobs

    Lists the jobs of one build (one per matrix entry), as jobs: each with its id, number (like 412.3), state, allow_failure, queue, started_at, finished_at and stage.

  • Get a job log

    Reads one job's build log as plain text in content (with ANSI color codes), to see which command failed and why.

Write 4

Create, change or send.

  • Start a build

    Starts a build of a repository's branch (the latest commit, or a given commit sha), the same as pushing, with an optional message shown on Travis CI.

  • Restart a build

    Restarts a build that finished or was canceled: all its jobs run again on the same commit.

  • Restart a job

    Restarts one job of a build that finished or was canceled, like a flaky test job, without running the others again.

  • Cancel a buildDeletes data

    Stops a running or queued build: it and its jobs become canceled.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Travis CI account.

What you enter

  • API token

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Travis CI data

    Ask a question in plain words. The agent can list repositories, get a repository or list a repository's builds in Travis CI, then answers with what it found.

  • 02

    Let an agent update Travis CI

    Have the agent start a build or restart a build in Travis CI as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Travis CI and Slack: it can list repositories in Travis CI and post a summary to a Slack channel in the same run.

FAQ

Travis CI and MyDeepAgents

Can MyDeepAgents connect to Travis CI?

Yes. The Travis CI connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Travis CI?

Paste an API key from your Travis CI account. You'll need: API token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Travis CI without asking?

Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.

Can I use Travis CI in workflows as well as agents?

Yes. Every Travis CI action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Travis CI to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.