Travis

User Management Commands

Following user management options are available in Travis Ci Enterprise (TCIE) versions.

These commands are run via the command line on the platform instance.

User Information in TCIE 3.x #

List basic information about users and their status.

kubectl exec -it [travis-api-pod]j /app/bin/users - list every user.

kubectl exec -it [travis-api-pod]j /app/bin/users --active - list every active user.

kubectl exec -it [travis-api-pod]j /app/bin/users --suspended - list every suspended user.

User Information in TCIE 2.x #

List basic information about users and their status.

travis users - list every user.

travis users --active - list every active user.

travis users --suspended - list every suspended user.

Suspend and Unsuspend Users in TCIE 3.x #

Suspend or unsuspend users. Builds triggered by suspended users are blocked by travis-gatekeeper.

kubectl exec -it [travis-api-pod]j /app/bin/suspend <login> - suspend a user where <login> is the user’s GitHub login.

kubectl exec -it [travis-api-pod]j /app/bin/unsuspend <login> - unsuspend a user where <login> is the user’s GitHub login.

Suspend and Unsuspend Users in TCIE 2.x #

Suspend or unsuspend users. Builds triggered by suspended users are blocked by travis-gatekeeper.

travis suspend <login> - suspend a user where <login> is the user’s GitHub login.

travis unsuspend <login> - unsuspend a user where <login> is the user’s GitHub login.

Please note: Using the suspend command does not restrict access to the Enterprise platform. It removes a seat restriction for an archived user. If a suspended user logs into the platform, the seat restriction would be imposed once more.

Difference between Active, Inactive, and Suspended Users #

  • Active User: User with a GitHub OAuth token and not marked as suspended.
  • Inactive User: User without a GitHub OAuth token and not marked as suspended.
  • Suspended User: User marked as suspended having a GitHub OAuth token or not.

Syncing a User in TCIE 3.x #

To sync a user (not technically part of User Management, but a related task):

To sync one user: kubectl exec -it [travis-github-sync-pod] bundle exec bin/schedule users [login]

To sync all users: kubectl exec -it [travis-github-sync-pod] bundle exec bin/schedule users

Please note: pod used for synchronizing users is github-sync-pod not travis-api-pod

Syncing a User in TCIE 2.x #

To sync a user (not technically part of User Management, but a related task):

To sync one user: travis sync_users --logins=<login>

To sync all users: travis sync_users

Contact Enterprise Support #

To get in touch with us, please write a message to enterprise@travis-ci.com. If possible, please include as much of the following as you can:

  • Description of the problem - what are you observing?
  • Which steps did you try already?
  • A support bundle (see table below on how to obtain it)
  • Log files from all workers (They can be found at /var/log/upstart/travis-worker.log - please include as many as you can retrieve).
  • If a build failed or errored, a text file of the build log
TCI Enterprise version Support bundle
3.x Run kubectl kots admin-console -n [namespace] to access admin console on http://localhost:8800
Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at: http://localhost:8800/app/tci-enterprise-kots/troubleshoot

A command for generating support bundle will appear after selecting:
If you'd prefer, [click here]() to get a command to manually generate a support bundle.
2.x+ You can get it from https://<your-travis-ci-enterprise-domain>:8800/support

Since the announcement in Q3 2020, the most up to date version of Travis CI Enterprise is 3.x line. There are not any new releases for version 2.2 and the support patches has been limited since March 2021 as well. For existing users of Travis CI 2.x we strongly recommend upgrading to the latest Travis CI Enterprise 3.x.

Have you made any customizations to your setup? While we may be able to see some information (such as hostname, IaaS provider, and license expiration), there are many other things we cannot see which could lead to something not working. Therefore, we would like to ask you to also answer the questions below in your support request (if applicable):

  • How many machines are you using / what is your Kubernetes cluster setup?
  • Do you use configuration management tools (Chef, Puppet)?
  • Which other services do interface with Travis CI Enterprise?
  • Which Version Control system (VCS) do you use together with Travis CI Enterprise (e.g. github.com, GitHub Enterprise, or BitBucket Cloud)?
  • If you are using GitHub Enterprise, which version of it?

We are looking forward to helping!