Releases: vyadh/teamcity-deployment-dashboard
v1.10.0
v1.9.0
- 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
v1.7.0
- 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
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
v1.4.1
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
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
v1.2.0
- 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