Legacy (Deprecated) Features
- 21 Jan 2023
- 2 Minutes to read
-
Print
-
DarkLight
-
PDF
Legacy (Deprecated) Features
- Updated on 21 Jan 2023
- 2 Minutes to read
-
Print
-
DarkLight
-
PDF
Like all DevOps, CI/CD and automation tools on the market, BuildMaster has evolved a lot over the years. The tools and libraries we use have also evolved, allowing us to develop better features with new technologies.
This page is an index of "deprecated" features that we plan to remove from the product in the coming years.
Legacy Features (Planned for Removal)
A "legacy feature" continues to function as coded, but will one day be removed.
While we continue to support their use, we strongly recommend moving away from them for two reasons:
- Legacy Features are Fragile; these features are rarely tested or used in practice, so the likelihood of regressions is higher when we ship new features
- Legacy Features are Poorly Documented; many legacy features weren't very well documented to begin with, and existing documentation may be incorrect. Especially if there are navigation instructions or screenshots.
This is a list of the current legacy features:
| Feature | Planned Removal | Replace With |
|---|---|---|
| Setup Templates | v2024 | just use the application description |
| Application Templates | v2024 | Application Backup / Restore -or- just clone existing application |
| Variable Value Renderers | v2024 | Custom Variable Rendering |
| Deployables | v2025 | Pipeline Variable Prompts |
| Release Templates | v2025 | Pipeline Variable Prompts |
| GitHub & GitLab Webhook Monitors | v2025 | Git Resource Monitors |
Deprecated (Legacy) Operations
A "deprecated operation" is something that your OtterScript may use. Like legacy features, these will continue to work as coded, but may one day be removed.
| Deprecated Operation | Replacement Operation |
|---|---|
AzureDevOps::Get-SourceGit::Get-SourceGitHub::Get-SourceGitLab::Get-Source |
Git::Checkout-Code |
AzureDevOps::TagGit::TagGitHub::TagGitLab::Tag |
Git::Ensure-Tag |
Deprecated operations will always give a warning if you use them, and migration is trivial; it only involves changing some OtterScript.
Removing Legacy Features
If a "legacy feature" is removed from newer versions of the product, you will not be able to upgrade to the newer version.
However, we will always provide a migration utility that will either migrate the data automatically or guide you on how to do so. This will be available in the final version that includes this feature - and which we will maintain for several years to come.
For example, if you use the "Setup Templates" feature (which will be removed in v2024), you will be prompted in v2023 to stop using it. If you attempt to upgrade to v2024 without taking these steps, the installer will block the installation.
The only features currently removed were developed a long time ago—i.e., before BuildMaster v5 (2016)—and then eventually removed in BuildMaster 6.2 (2020). These are documented in detail at BuildMaster 6.1 Legacy Features.
Was this article helpful?
