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

Release 3.0.33

 

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

Releases 3.0.31-3.0.32

 

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

Release 3.0.30

 

Patch

  

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

Release 3.0.29

 

Patch

  

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

Releases 3.0.26-3.028

 

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.

Release 3.0.25

 

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:

Release 2.2.24

 

Patch

 

 

Bug fixes

  • scala sbt-extras version updated
  • fixed issue with temp dir creation on worker

Known Issues

  • Migrations and database creation are not run by default on startup when in HA mode. Have to run te-db-migrate and then te-db-migrate-logs manually on the platform host.
  • In HA mode canceling an individual job of a build matrix can return a 502.
  • HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.

Release 2.2.23

 

Patch

 

 

Bug fixes

  • improved Redis communication
  • added safelists for Bionic builds
  • fixed postgres issue when using latest Xenial based workers
  • added c/c++ defaults for FreeBSD

Known Issues

  • Migrations and database creation are not run by default on startup when in HA mode. Have to run te-db-migrate and then te-db-migrate-logs manually on the platform host.
  • In HA mode canceling an individual job of a build matrix can return a 502.
  • HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.

Release 2.2.21

 

Patch

 

 

Bug fixes

  • Fixed travis console access

Known Issues

  • Migrations and database creation are not run by default on startup when in HA mode. Have to run te-db-migrate and then te-db-migrate-logs manually on the platform host.
  • In HA mode canceling an individual job of a build matrix can return a 502.
  • HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.

Release 2.2.20

 

Patch

 

 

Bug fixes

  • Various security updates
  • Fix for 'follow logs' button position in job view
  • Added logout method to API

Known Issues

  • Migrations and database creation are not run by default on startup when in HA mode. Have to run te-db-migrate and then te-db-migrate-logs manually on the platform host.
  • In HA mode canceling an individual job of a build matrix can return a 502.
  • HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.