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.
Release 2.2.18
Patch
michal@travis-ci.org, Product Manager
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.
Release 2.2.16
Patch
michal@travis-ci.org, Product Manager
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.
Release 2.2.15
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.
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.
Release 2.2.13
Patch
Bug Fixes
Fixed "Timeout waiting for network availability" delay in builds.
Fixed issue when trying to override the default build environment.
Fixed issue with SauceLabs sauce_connect addon.
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.
Release 2.2.12
Patch
Bug Fixes
Travis CI Enterprise will now perform log rotation correctly.
Travis CI web GUI now refreshes automatically and does not require a browser refresh.
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
Release 2.2.11
Patch
Bug Fixes
Fixed support for Ubuntu Xenial in Override Default Build Environment option in the Admin Dashboard.
Known Issues
Travis CI Enterprise will still write to the old log after log rotation.
Migrations and database creation are not run by default on startup when in HA mode. You 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.
Release 2.2.10
Patch
Bug fixes
Switching between Java versions fixed in Xenial build images.
Xenial build images now use systemctl instead of service.
Branches UI now displays the most recent build run even if done by trigger build API.
Better error messaging in UI for syncing initial repositories.
Known Issues
Travis CI Enterprise will still write to the old log after log rotation.
Migrations and database creation are not run by default on startup when in HA mode. You 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.
Release 2.2.9
Patch
Features
Build and Job endpoints now include a log_complete attribute
Known Issues
Travis CI Enterprise will still write to the old log after log rotation.
Migrations and database creation are not run by default on startup when in HA mode. You 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.
