Travis CI Enterprise release notes enterprise.travis-ci.com

Major

Patch

• logs access limitation (https://docs.travis-ci.com/user/disable-job-logs)
• Hashicorp Vault integration (https://docs.travis-ci.com/user/hashicorp-vault-integration)
• added cri-dockerd service
• fixed 'review and add' organizations link
• fixed organization management links
• fixed repository migration text
• security updates

(This version requires k8s 1.21+)

Minor

Patch

• Security updates
• RollingUpdate and replicas increase are available now under a flag (turned off by default - 'low resources' config option in 'advanced settings')

Major

Patch

• 'restarted by' information available in job info
• HPA configuration; BETA - can be enabled in KOTS admin-console configuration in 'advanced settings')
• Security updates
• Deployment changes, now using 2 replicas with RollingUpdate strategy for each service for non-KURL installations

Minor

Patch

• GitHub App tokens can have now additional rights (configurable from admin console)
• Fixed usage of custom SSH Key for GitHubApp-enabled public repositories
• Release tag content fixed for auxiliary container (provides exact Travis CI Enterprise version instead of latest)
• Security updates

Minor

Patch

• added possibility to set global notification webhooks
• job query optimizations(in beta, needs to be enabled in 'advanced settngs' section)
• fixed api console

Major

Technical upgrade of Travis CI Enterprise software stack.

• Ruby on Rails version upgrade
• Puma version upgrade
• Sinatra version upgrade
• Rack version upgrade
• Rake version upgrade
• Code updates to accomodate to upgraded frameworks

Patch

Removing unnecessary calls to Stripe in Travis CI Enterprise (cleanup of codebase shared with Travis CI).

Patch

Minor fix for crashing Travis Admin when Version Control System other than GitHub is used by the user account.

Patch

Minor bugfixes for integration with GitLab Enterprise/Community Edition (Beta feature) related to access rights scope requested by Travis CI Enterprise.

Now Travis CI Enterprise 3.x will not request docker registry access rights when signing up using GitLab.

Minor

New Git repository settings introduced: Security Settings. These allow to determine whether the repository will share encrypted environment variables and (in case of private repositories) Custom SSH Keys with the forks of a particular repository when a pull request in fork-to-base collaboration model would trigger build at Travis CI.

Repositories activated in Travis CI Enterprise before March 1st, 2022 will have the Share encrypted environment variables with forks (PRs) setting set to OFF. Please verify your collaboration model if necessary (especially for public repositories). The Share SSH keys with forks (PRs) will be set to ON in order to not break too many existing collaboration set ups.

Repository settings will be set by default to OFF for any repository activated in Travis CI Enterprise after March 1st, 2022. For repositories activated in Travis CI Enterprise after March 1st, 2022 you may want to consider changing the default settings depending on your collaboration model.

Read more:

• Blog post about the change
• Encryption keys in public Travis CI documentation
• Private dependencies in public Travis CI documentation, particularly Custom SSH Key section