Release 2.2.12

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

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

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

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.

Release 2.2.8

Security Fixes

  • System packages have been updated to their latest security versions.

Bug fixes

  • Adds tool to migrate existing repositories connected to Travis CI Enterprise using deprecated GitHub Services to instead use Webhooks. See the enterprise documentation for usage instructions.

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.7

Security Fixes

  • System packages have been updated to their latest security versions.
  • Updates Slanger to latest version (0.6.1) to address RCE vulnerability.

Bug fixes

  • Fixes an issue where builds were not correctly using Xenial workers even if the correct configuration was provided.
  • GitHub webhook creation will now correctly respect the 'disable ssl verification' option found in settings.

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. 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.6

Security Fixes

  • System packages have been updated to their latest security versions.

Bug fixes

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. 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.5

Security Fixes

  • System packages have been updated to their latest security versions.

Bug Fixes

  • GitHub service hooks migrated to web hooks due to deprecation. See travis-api PR for more details. If using a self-signed certificate SSL verification for webhooks will need to be disabled.
  • Adding head_commit and base_commit to request renderer (see travis-api #840 for details)
  • Fixed About Us appearing in the top navigation bar.

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. 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.4

Security Fixes

  • System packages have been updated to their latest security versions.

Bug Fixes

  • Fixed issue where head_commit and base_commit information wouldn't be transmitted correctly in webhook notification. See travis-tasks PR and travis-hub PR for more details.

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. 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.3

Security Fixes

  • System packages have been updated to their latest security versions.
  • Public repositories' deploy keys are read-only (no longer read-write). Configure additional SSH keys in repositories' settings, as needed.

Bug Fixes

  • You can now add a custom CA bundle in the Replicated settings which was required for some self-signed certs, and some SSL certificates.
  • Fixed issue with Travis CLI not being able to login to Enterprise 2.2.2 servers

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. 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

No published changelogs yet.

Surely Travis CI Enterprise will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree