All integrationsCode Repositories

Travis CI

Request Travis CI builds on any branch or commit with config overrides and see what Travis CI made of each request, list builds, and manage a repository's environment variables and cron jobs.

actions
13

Actions

Steps a workflow can run in Travis CI.

  • List repositoriesList the repositories you can see in Travis CI, active ones by default, with each one's id, slug, default branch and whether Travis CI builds it.
  • Get repositoryGet one repository: its Travis CI id, default branch, whether Travis CI builds it, and its most recently started build.
  • List branchesList the branches Travis CI knows for a repository, each with its latest build, or check one branch's status by its name.
  • List buildsList a repository's builds, newest first, optionally only on one branch, in some states or started by some events.
  • Trigger buildAsk Travis CI to build a branch, optionally a given commit, with a message and config overrides. Travis CI decides on the request moments later: Get request, with the request id this returns, shows the build or the reason there is none. Builds only run once a plan is selected in Travis CI. It accepts 10 such requests per repository an hour.
  • Get requestGet a build request, such as one from Trigger build: whether Travis CI approved or rejected it, its message (for a rejection, the reason, such as no plan selected), what it noticed in the config, and any builds made from it.
  • List environment variablesList a repository's environment variables: name, id, branch, and the value of each public one. Travis CI never returns a private variable's value.
  • Create environment variableAdd an environment variable to a repository's builds, for every branch or one. A private variable's value is hidden in build logs and never shown again. A name already used on the same branch is refused: use Update environment variable.
  • Update environment variableChange an environment variable's value, name, branch or whether its value shows in build logs. Only what you fill in changes.
  • Delete environment variableDelete an environment variable from a repository.
  • List cron jobsList a repository's cron jobs: the branch each one builds, how often, and when it runs next.
  • Create cron jobBuild a branch daily, weekly or monthly. A branch has at most one cron job, so this replaces any it already has.
  • Delete cron jobDelete a repository's cron job. It is checked to belong to the repository first, so a mistyped id can't remove another one.

Automate Travis CI with Lodol.

Connect Travis CI and ask your AI for your first workflow.

Free plan, no credit card