Skip to content

Releases: vyadh/teamcity-deployment-dashboard

v1.10.0

18 Jul 08:33
Compare
Choose a tag to compare
  • Support for showing custom properties on deployments such as a branch name #21
  • Fixed issue where pressing return in the deploy search navigated away from the page #19
  • Document build process and add Docker build and scripts for simplicity #23

v1.9.0

19 Jul 07:18
Compare
Choose a tag to compare
  • Support for resolving property references in project/version/environment. For example, using a build number from a build stage (via snapshot-dependency) to show appropriate version at deployment #14
  • Make it more obvious that only 'deployment' builds are shown in dashboard #16
  • Ignore whitespace in environment names to avoid unnecessary confusion when deployments are not found #15

v1.8.0

14 Jul 22:41
Compare
Choose a tag to compare
  • Visualise hanging builds
  • Case-insensitive sorting of project names
  • Fixed visual spacing issue between project and deployment columns

v1.7.0

14 Jul 09:51
Compare
Choose a tag to compare
  • Make the header sticky so it can be seen when scrolling through a large number of projects
  • Avoid wrapping long project names unnecessarily #11
  • Better use of horizontal space by using CCS grid to shrink/grow to certain limits
  • Remove rather redundant 'Project' name column header
  • Fixed minor spacing and font issues

v1.6.0

12 Jul 21:19
Compare
Choose a tag to compare

Case-insensitive environment matching: The case of the environment displayed is now normalised to that specified in the configuration of the dashboard. As well as being case-insensitive, this allows better user facing labels, e.g. a environment of 'uat' can become 'UAT' and 'develop' can become 'Develop' by configuring as such in the environment list. #6

Now obfuscates any passwords. This avoids the plugin being used as a vector for uncovering TeamCity secrets.

v1.5.0

07 Jul 15:32
Compare
Choose a tag to compare

Provided optional deep build history search to find different environments deployed to from the same build configuration, rather than the default mode that only looks at the last deployment. Resolves #6

v1.4.1

02 Jul 22:14
Compare
Choose a tag to compare

Support use of multiple build configurations that deploy to the same project/environment (e.g. one per branch). This required resolving duplicates of project/environment, which before was being done incidentally, but now the dashboard plugin picks the latest deployment by time of run. Fixes #7

v1.4.0

30 Jun 20:59
Compare
Choose a tag to compare

Support specifying version from a configuration property as well as the previous build number mechanism. This makes it easier to provide a semver formatted string to the dashboard at the same time as presenting the build number in a separate way, which is useful as it may contain other metadata.

v1.3.0

27 Jun 22:13
Compare
Choose a tag to compare
  • Added support for non-version information in build numbers by ignoring everything after the semver format string that is separated by a space.
  • Added information to docs on how the dashboard uses TeamCity build number versioning

v1.2.0

23 Jun 08:31
Compare
Choose a tag to compare
  • Changes mechanism for discovering builds in order to use ones not on the default branch. Fixes #2
  • Fixed running Gradle tests outside of IntelliJ
  • Clarified environment and project keys can be system properties and environment variables as well as configuration properties
  • Updated Kotlin to v1.3.40