LATEST VERSION: 1.2 - RELEASE NOTES
Scheduler for PCF v1.2

Scheduler for PCF Release Notes

This topic contains release notes for Scheduler for Pivotal Cloud Foundry (PCF).

v1.2.25

Release Date: April 22, 2019

Features included in this release:

New features and changes in this release:

  • Enable MySQL native passwords and accept usernames with @ symbols for better Azure support.

Known Issues

There are no known issues for this release.

v1.2.23

Release Date: February 21, 2019

Features included in this release:

New features and changes in this release:

  • Fixed issue: Scheduler cannot install in an internetless environment
  • Scheduler dependencies are pre-compiled and no longer fetched at install.

Known Issues

There are no known issues for this release.

v1.2.5

Release Date: December 6, 2018

Breaking Change: Any automated process that updates Scheduler for PCF breaks if the deployment has TLS enabled on the MySQL database. For information about configuring TLS in MySQL for PCF, see Configure Security.

Features included in this release:

New features and changes in this release:

  • Updated OpenJDK
  • Updated MariaDb Connector

Known Issues

  • Scheduler cannot install in an internetless environment.

v1.2.3

Release Date: September 24, 2018

Features included in this release:

Breaking Change: Any automated process that updates Scheduler for PCF might break if the deployment does not use a Xenial stemcell.

The new feature in this release:

Known Issues

There are no known issues for this release.

v1.2.0

Release Date: July 5, 2018

Features included in this release:

The new feature in this release:

  • The API for Scheduler for PCF now includes ability to retrieve all schedules for jobs in a space. For information, see the Scheduler for PCF API docs.

Known Issues

There are no known issues for this release.

View Release Notes for Another Version

To view the release notes for another product version, select the version from the dropdown at the top of this page.

Create a pull request or raise an issue on the source for this page in GitHub