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

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.

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.

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.

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.

Patch

Bug Fixes

• The client_secret removed from gatekeeper log
• Removal of duplicated cron jobs from database
• Not enabling i386 architecture for packages for s390x in order to prevent apt-get update errors
• Fix for no_proxy not honored by travis-tasks (eg GitHub status updates, Slack Updates, etc).
• S3 cache settings fixed - Travis CI Enterprise builds should cache artifacts properly when building R project

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.

Patch

Bug Fixes

• When using a GitHub Enterprise instance in Private Mode, user/repository avatar images will not show up in emails nor will the build status image in repository README files.
• When using a self-signed cert some images may not show in some email clients.
• Sonarcloud CLI could not be fetched - now it’s fetched via https
• Maven repositories could not be reached - default mirror url is https now, TRAVIS_MAVEN_CENTRAL_MIRROR variable introduced to hold the mirror configuration

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.
• no_proxy not honored by travis-tasks (eg GitHub status updates, Slack Updates, etc).
• HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.

Patch

Bug Fixes

• Logs not updating correctly when browsing "My Repositories" in the GUI fixed
• Custom apt mirror source exposed in Replicated dashboard. This will update the TRAVIS_BUILD_APT_MIRRORS_UNKNOWN environmental variable

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.
• no_proxy not honored by travis-tasks (eg GitHub status updates, Slack Updates, etc).
• When using a GitHub Enterprise instance in Private Mode, user/repository avatar images will not show up in emails nor will the build status image in repository README files.
• When using a self-signed cert some images may not show in some email clients.
• HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.

Patch

Bug Fixes

• Fixed log_complete Build API endpoint regression.

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.
• no_proxy not honored by travis-tasks (eg GitHub status updates, Slack Updates, etc).
• When using a GitHub Enterprise instance in Private Mode, user/repository avatar images will not show up in emails nor will the build status image in repository README files.
• When using a self-signed cert some images may not show in some email clients.
• HTTPS clones fail when GitHub Enterprise instance is using a self-signed cert.