BuildMaster Downloads & Release Notes
We like to ship new versions of BuildMaster fairly often, both to fix bugs/annoyances and to introduce new functionality. However, just because there's a new version available, that doesn't mean you need to install it. Take a look at When should I update BuildMaster? to learn more.
BuildMaster 6.2 - Supported
- BM-3636 - Add option to Execute-DatabaseStatement to disable writing statement to execution log
- BM-3639 - FIX: Add support for Invoke-Plan and Invoke-Module in pre/post deployment steps
- BM-3634 - FIX: BuildMaster agent host process is not always allowing TLS 1.2 connections
- BM-3637 - FIX: Marking manual tasks complete on parallel executions may mark wrong task complete
- BM-3635 - FIX: Operations with multiple aliases for the same required argument raise compiler error unless all aliases are specified
- BM-3638 - FIX: Server acquisition and initialization can cause deadlocks
- BM-3633 - Add message about number of releases impacted when deleting a pipeline
- BM-3620 - Build variable prompts not prompting when Create New Build from menu
- BM-3623 - Fix added an OtterScript Module to your plan via the Visual Editor shows an error
- BM-3621 - Fix Compare-Directories will not show cs file differences
- BM-3624 - Fix default filter on Build History Page not working
- BM-3616 - Fix view execution details returns a 403 with a requirement of ReleasePackages_ViewDeploymentLogs when the user has that task.
- BM-3618 - FIX: Build creation/promotion logic causes database deadlocks
- BM-3619 - FIX: Build/Deploy API does not properly consider release variable templates
- BM-3632 - FIX: Configuration files on the release overview page may display incorrect version data
- BM-3588 - FIX: Dependent Roles aren't imported from Otter
- BM-3626 - FIX: EventListenerRunner may not process variable replacements
- BM-3627 - FIX: Post-deployment steps in pipeline may fail to resolve variables
- BM-3631 - FIX: Reduce "invalid pipeline name" errors by removing PipelineIdShim
- BM-3628 - Update Inedo.Ssh to 2.1.0
- BM-3617 - FIX: Invalid Pipeline causes Object Reference error on My Approvals
- BM-3595 - Add additional options for applying template applications
- BM-3614 - FIX Editing an existing configuration will remove the `=` from any value
- BM-3607 - Fix: Config Preview On Deploy
- BM-3599 - Copy previous release variable values when Pipeline auto-creates the release
- BM-3610 - Deployment plan execution and dispatch performance improvements
- BM-3600 - FIX: "Run isolated" is ignored in Visual Editor
- BM-3607 - Fix: Config Preview On Deploy
- BM-3609 - FIX: Execution dispatcher can sometimes get temporarily stuck
- BM-3611 - FIX: Latest Build link /releases is incorrect
- BM-3612 - Update Inedo.ExecutionEngine to v100.0.1
- BM-3608 - Update InedoLib to v800.3.5
- BM-3605 - Add logging for exceptions in TaskRunner auto-dispatch
- BM-3602 - FIX: Add approval internal API doesn't verify group membership
- BM-3603 - FIX: Encrypted Global Credentials Cannot be used in the $SecureCredentialProperty variable function
- BM-3601 - FIX: Select Artifact Page does not consider application scope when checking permission
- BM-3594 - FIX: Error when managing calendar views with global views
- BM-3598 - FIX: Execution in progress page checks for Admin_ConfigureBuildMaster permission on some executions
- BM-3596 - FIX: Manage Deployables on Create Build Page has incorrect links, Deployables not shown on overview
- BM-3592 - Fix: Multiple Change Reports showing on a build causing slow load times on the Build Page
- BM-3597 - FIX: Release deployments endpoint may return null for certain values
- BM-3593 - Update Inedo.SDK to v1.7.4
- BM-3591 - FIX: BuildNumber in UI is restricted to 10 characters instead of 50
- BM-3583 - FIX: Error Restoring Application using Merge Configuration Option
- BM-3587 - FIX: Javascript error when filtering by StageName and Status on Deployment History without a Release
- BM-3589 - Update Inedo.SDK to v1.7.3
- BM-3585 - Add config setting to enable new extension loader to eliminate locking issues
- BM-3581 - Allow application backup/restore using a file system directory feed
- BM-3586 - FIX: Create-Release operation mishandles release templates
- BM-3582 - FIX: Error restoring applications using the rename option causes unique constraint errors
- BM-3580 - FIX: Release API's list deployments endpoint may fail in pre-6.2 executions
- BM-3584 - Update InedoLib to v800.3.0
- BM-3574 - FIX: Add link to navigate to resequence releases
- BM-3572 - FIX: Error creating Execute Otterscript Plan Event Listener
- BM-3573 - FIX: Missing icons in application overview
- BM-3575 - FIX: Object reference error on Edit Release Template Page with an invalid Url
- BM-3576 - FIX: Releases with a NULL pipeline cause load errors
- BM-3579 - Inedo.SDK: Upgrade from 1.7.1 to 1.7.2
- BM-3578 - Only check for "Legacy.NoLegacyFeaturesDetected" during 6.1 Database Upgrade
- BM-3577 - Reject build should only cancel pending executions, not executing executions
- BM-3571 - Update Inedo.ExecutionEngine to v100.0.0
- BM-3570 Open - FIX: CSS Regression causes admin link to not drop-down menu
- BM-3521 - Add RenameScriptPage
- BM-3567 - Display pipeline stage creation/cancellation user information on pipeline target execution details page
- BM-3554 - FIX: API Call to /api/json/Rafts_CreateOrUpdateRaftItem errors on ModifiedOn_Date
- BM-3566 - FIX: Deployment history filter duplicate stage names and build numbers
- BM-3563 - FIX: Log output is not automatically scrolling to the bottom when executing a deployment plan
- BM-3561 - FIX: Null reference exception when attempting to save proxy settings
- BM-3565 - FIX: Release API's Deploy build method does not attach variables to deployment
- BM-3547 - FIX: Release API's Deploy method returns stage executions instead of stage target executions
- BM-3562 - Improve performance for Git raft operations
- BM-3568 Open - Build Promotion Details not showing Approval Details
- BM-3559 - Add additional fields to ContainerSourceSetting on Setup Templates
- BM-3550 - Deploy Template Variable not Prompting on Initial Deploy
- BM-3509 - Display configuration file description on config file overview page
- BM-3548 - FIX: "Module not Found" error in visual editor for application-based modules
- BM-3553 - FIX: "The WebResource.axd handler must be registered in the configuration to process this request." on some pages in integrated mode
- BM-3557 - FIX: Error cloning application
- BM-3552 - FIX: Error editing issue tracker sources that use legacy resourcecredentials
- BM-3556 - FIX: Error renaming global pipelines
- BM-3558 - FIX: Modules may be imported as Deployment Plans
- BM-3555 - FIX: Target not found in pipeline stage error when sequential targets are selected in the pipeline editor
- BM-3549 - FIX: Upgrade inedosql to 1.0.3
- BM-3551 - InedoLib: Upgraded from 801.1.0 to 800.2.0
- BM-3547 Open - FIX: Release API's Deploy method returns stage executions instead of stage target executions
- BM-3532 - [Database] Renamed BuildExecutions_Extended to PipelineStageTargetExecutions_Extended
- BM-3533 - [NativeAPI] Removed Builds_GetExecutionExtended, Renamed Builds_GetExecution to Builds_GetPipelineStageTargetExecution
- BM-3537 - Added $SecureResourceProperty variable function
- BM-3541 - Don't display all stages on the pipeline editor
- BM-3546 - FIX: "global::" prefix may get lost in visual plan editor and yield "template not found" display error
- BM-3538 - FIX: $CredentialProperty function cannot find non-legacy credentials
- BM-3534 - FIX: $ExecutionUser is always set to SYSTEM
- BM-3527 - FIX: Build-queueing operations fail if Wait is set to true.
- BM-3531 - FIX: Cannot filter by global pipelines on list releases page
- BM-3535 - FIX: Cannot view some pre-upgrade build executions
- BM-3539 - FIX: Deployment variables may injected into the wrong stage executions
- BM-3540 - FIX: Error loading application overview page if release pipeline doesn't exist
- BM-3528 - FIX: Error rendering SOAP API Help File
- BM-3544 - FIX: Error when trying to re-sequence environments
- BM-3542 - FIX: External infrastructure sync configuration only accepts secured resources for BuildMaster and not Otter
- BM-3545 - FIX: Invalid Pipeline for releases created with XML-based (pre-6.2) release templates that specify a global pipeline
- BM-3543 - FIX: Manual approvals should trigger approval verification immediately
- BM-3536 - Inedo.SDK: Upgrade from 1.7.0 to 1.7.1 (FIX: Rafts export OtterScripts with .otter extension)
- BM-3510 - Add "Server Pool" to server targeting on pipeline targets
- BM-3511 - Add Variables, Comments to Scheduled Promotions
- BM-3512 - Add warning when variable expressions in configuration files cannot be replaced at deploy time
- BM-3524 - Expose Rafts_RenameRaftItem, Rafts_CreateOrUpdateRaftItem Native API Methods
- BM-3530 - Expose Variables_GetDeploymentVariables via API and do not delete DeploymentVariables after dispatching execution
- BM-3522 - FIX: ApplyTemplate Execution Should import Webhooks, Repo Monitors, Variables, and Variable Renderer
- BM-3520 - FIX: Build history page doesn't filter by release
- BM-3516 - FIX: Cannot create application-scoped secure resources from application resources page
- BM-3519 - FIX: Error received on trying to change a build with no release to have a release
- BM-3517 - FIX: Pipeline with invalid stage name causes the editor to crash
- BM-3518 - FIX: Secure Resources, Secure Credentials Page UI Filtering
- BM-3513 - FIX: Variables injected from a release template not always available to a plan specified as a pipeline stage target
- BM-3523 - FIX: Various changes to build overview page and package listing
- BM-3498 - FIX: Configuration file template variable replacement does not work
- BM-3505 - FIX: Nested executions in invoke script operations may not report proper status
- BM-3507 - FIX: Pipeline stages of deployed builds may appear out of order
- BM-3502 - FIX: Remote Database Operations fail with "Cannot decrypt persistent property; decryption key not configured"
- BM-3499 - FIX: Text template navigation
- BM-3506 - FIX: Traditional installer is not allowing upgrades from 6.1 to 6.2
- BM-3501 - FIX: Update Inedo.Agents to v46
- BM-3497 - FIX: Error on upgrade when an application script asset has the same name as a global script asset
- BM-3492 - Add BuildNumber argument to Deploy-Build operation
- BM-3495 - FIX: Cannot perform direct upgrade to 6.2
BuildMaster 6.1 - Supported
- BM-3606 - FIX: backing up applications with spaces in the name will cause 400 errors on upload
- BM-3560 - FIX: Example Legacy Source Control Provider from BuildMaster v3 isn't displayed on legacy providers page, preventing upgrade
- BM-3494 - FIX: "Add Container" Link on application release page goes to "Add Package"
- BM-3508 - FIX: Infrastructure sync for roles can fail if there are roles in the current instance that share the same set of servers
- BM-3529 - FIX: Legacy Feature Detector Improperly Checks for Deployables Prior to Upgrade
- BM-3525 - FIX: The Create Role endpoint in the Infrastructure API should not require content body when the entity name is supplied in the URL
- BM-3514 - Replace inline upgrade release notes with information link
- BM-3504 - FIX: Add delete button to Delete Legacy Configuration Profiles on the Legacy Dashboard
- BM-3500 - FIX: Incompatible extension versions are being offered as updates
- BM-3496 - FIX: Legacy feature checker does not consider the correct legacy features when setting the NoLegacyFeaturesDetected value
- BM-3493 - FIX: Application backup can generate incorrect execution log data [regression]
- BM-3488 - Add description to edit extension configuration variable page
- BM-3490 - Add more detailed progress for application exporting
- BM-3489 - Backport backup/restore functionality from v6.2 branch
- BM-3486 - FIX: Infrastructure Sync can fail when roles with 0 servers are present in the source
- BM-3481 - Deprecate Association of Issues and Builds feature
- BM-3485 - FIX: Build and Release API JSON input parsing fails to map certain properties
- BM-3482 - FIX: Create Release endpoint does not handle deployable versions or imported deployables
- BM-3483 - FIX: InedoAgent impersonation may not work with limited user accounts
- BM-3474 - FIX: Pipelines with legacy components that can't be deserialized crashed All Applications page
- BM-3475 - FIX: Unit test results spanning multiple groups will only link to the first group on the build overview page
- BM-3484 - Update Inedo.Agents to v46.0.0 and Inedo.Agents.Client to v547.0.0
- BM-3457 - All non-system admins to manage scoped resource credentials
- BM-3480 - FIX: Cannot edit/delete a configuration file with no instances
- BM-3473 - FIX: Error saving Advanced Application Settings when new navigation isn't enabled
- BM-3477 - FIX: null configuration file versions are improperly imported
- BM-3476 - FIX: Potential extension manager initialization deadlock
- BM-3471 - FIX: Release deployables cannot be set via query string in the Create Release API endpoint
- BM-3470 - Hide deployables by default on new installations (6.2 Preview)
- BM-3479 - Update Inedo.Agents from v44 to v45
- BM-3478 - Update InedoLib to v542
- BM-3464 - Assigned user field of Manual Operation now defaults to $ExecutionUser
- BM-3466 - FIX: "Authenticated," "Everyone" pseudo-groups do not work in manual group approvals
- BM-3456 - FIX: Invalid Encryption Key or Configuration Yields Server Uneditable
- BM-3462 - FIX: IssueSource enumeration may not always include application id in UI
- BM-3465 - FIX: View_Application privileges allow sensitive variables to be edited and seen in JSON mode
- BM-3463 - Improve application setup & templates (6.2 Preview)
- BM-3467 - InedoLib: Update from 540 to 541
- BM-3461 - Add "Advanced Template Export" page (6.2 preview)
- BM-3460 - FIX: Imported applications may not have correct 6.2 preview navigation enabled
- BM-3458 - FIX: Importing applications with global pipelines may cause import errors
- BM-3459 - Include build artifact metadata in application backups
- BM-3383 - Include servers property in "list roles" endpoint of the Infrastructure Management API
- BM-3454 - Add Reject-Build operation
- BM-3452 - FIX: Automatic activation (and other third-party services) fail due to inedo.com site migration
- BM-3451 - FIX: $PackageVersion function should only consider active packages
- BM-3449 - FIX: Execution status from "force normal" or "force warn" statements are not recorded correctly as final execution result
- BM-3440 - Inedo.SDK: Upgrade from 1.5.0 to 1.6.0
- BM-3448 - Allow variable expansion in "async" and "lock" execution directive values
- BM-3443 - FIX: Edit/Create Package Source page should allow Inedo Product credentials as well as Username & Password credentials
- BM-3447 - FIX: Exceptions from variable approval when evaluating a function
- BM-3434 - FIX: Execution log scopes created asynchronously can get assigned an incorrect parent scope
- BM-3444 - FIX: Missing System.ValueTuple dependency on BuildMaster agent host process
- BM-3441 - FIX: Multi-scoped variables may incorrectly cascade
- BM-3442 - FIX: Sequential executions are not cancelled if a previous plan execution in the same pipeline stage fails
- BM-3399 - Improve execution logger performance
- BM-3439 - Update Inedo.ExecutionEngine to v74.0.0
- BM-3445 - Update InedoLib from v539.0.0 to v540.0.0
- BM-3433 - Add Create-BuildVariable Operation
- BM-3433 - Add Create-BuildVariable Operation
- BM-3435 - Add versioning for application templates (6.2 preview)
- BM-3435 - Add versioning for application templates (6.2 preview)
- BM-3418 - FIX: Inedo Agent fails to execute some operations if Windows PowerShell is not installed
- BM-3364 - FIX: Invalid variable value formatting in bulk-edited pipeline variables is not validated until execution time
- BM-3437 - FIX: WebHooks and Repository Monitors should not be system-unique
- BM-3431 - FIX: Custom Plans in GitHub Webhook do not capture $Branch and $CommitId as Runtime Variables
- BM-3430 - FIX: Formatting is incorrect for NuGet packages attached to builds
- BM-3432 - FIX: Mocks:: operations may be used in place of Windows:: if namespace isn't explicitly set
- BM-3429 - FIX: System-level issue source refresh fails
- BM-3234 - Add ability to filter by environments in Server Error event listener
- BM-3417 - Add application permissions page (6.2 preview)
- BM-3428 - Add configuration file editor types (6.2 Preview)
- BM-3427 - Add Container sources (6.2 Preview)
- BM-3424 - Add Setup Templates Feature (6.2 preview)
- BM-3423 - Add unified scripts page (6.2 preview)
- BM-3415 - Calculate package hash if not provided via IPackageManager interface from an operation
- BM-3419 - FIX: Application-level resource credentials don't work for issue sources
- BM-3425 - FIX: Change SecuredLink base class to enable operation on simple pages
- BM-3396 - FIX: Deployments for inactive applications should not appear in the Recent Deployments tab
- BM-3418 - FIX: Inedo Agent fails to execute some operations if Windows PowerShell is not installed
- BM-3416 - FIX: List variable sources do not handle errors correctly
- BM-3412 - FIX: New application navigation's z-index interferes with administration and user dropdown menu (6.2 preview)
- BM-3411 - FIX: Package source deletion fails with database error (6.2 preview)
- BM-3413 - FIX: PreviewFeatures.HideHomePageMessage setting is ignored (6.2 preview)
- BM-3407 - FIX: Show hidden for resource credential doesn't show value in some circumstances
- BM-3405 - Inedo.SDK: Upgrade from 1.4.0 to 1.5.0
- BM-3422 - New application variables page (6.2 preview)
- BM-3420 - Render application descriptions using Markdown
- BM-3414 - Typos in application setup template text (6.2 preview)
- BM-3421 - Upgrade Inedo.Agents.Client to v546.0.0
- BM-3409 - Add 6.2 Preview Features (New Nav, App Templates, Packages)
- BM-3398 - Add release filtering/targeting to build triggers
- BM-3397 - Add scheduled build triggers (applications) & scheduled jobs (system)
- BM-3390 - Add Script UUID to "Change Script Details"
- BM-3400 - Add support for "Default" release templates
- BM-3404 - Add support for run-as user and process isolation
- BM-3381 - Combine Repository Monitors and Webhooks into "Build Triggers"
- BM-3410 - FIX: Extension loader conflicts between legacy (.bmx) and new extensions (may require deleting .bmx files in extensions folder, then restarting web/service)
- BM-3378 - FIX: Pipeline Stage Group Approval Notification Error
- BM-3382 - Lazy load active releases on the Application Overview page when there are more than 5
- BM-3406 - Update Inedo.ExecutionEngine to v73
- BM-3401 - Update to Inedo.Agents v44.0.0
- BM-3402 - Update to Inedo.Agents.Client v543.0.0
- BM-3408 - Update to Inedo.SDK v1.4.0
- BM-3403 - Update to InedoLib v539.0.0
- BM-3387 - Add "active", "parentName" property to environments in Infrastructure API
- BM-3388 - Add health check and version information endpoint at /health
- BM-3379 - Allow application-scoped credentials, that can optionally inherit/override values from a parent set of credentials
- BM-3392 - Clarify CEIP message
- BM-3394 - FIX: Attempting to access an empty secret from the $CredentialProperty function generates an "object reference not set" error
- BM-3393 - FIX: Release templates that can't be deserialized crash release templates page
- BM-3376 - Add "Recent Deployments" section to the BuildMaster overview page
- BM-3386 - Add undisclosed to "Web.LatestNewsDisabled" (All Settings)
- BM-3380 - FIX: Inedo agent upgrade button link is incorrect
- BM-3385 - FIX: Servers require Force SSL to be True in order to keep encryption type of SSL.
- BM-3374 - Add "Everyone" and "Authenticated" pseudo-groups
- BM-3375 - Add Hybrid User Directory
- BM-3247 - Display pipeline stage target when a stage has multiple targets for deployments titles/links
- BM-3368 - FIX: Making changes to a user account on the edit user page causes group memberships to be reset
- BM-3369 - Add ID ("bm-login-button") to login button
- BM-3366 - Add Multi-Directory user directory
- BM-3373 - FIX: Cannot log out as a user with no privileges
- BM-3370 - Rename "Upgrade Agents" button to "Select Servers to Update..." and filter list of default servers
- BM-3239 - Add Invoke-Plan, Invoke-Module, and Invoke-OtterScript Operations
- BM-3359 - Add search box and filters on System Variables page
- BM-3361 - FIX: ssh agent batch file copy fails
- BM-3362 - FIX: UI Issue - bottom banner hides info
- BM-3360 - Server "Error logging" option seems to be ignored
- BM-3363 - Unit Tests page can't filter by "all"
- BM-3352 - Add ability to set Parent Environment on Create, Edit Environment
- BM-3344 - Add skeleton groups to auto-generated build and deployment plans
- BM-3356 - Allow release pipeline to be changed without rejecting all builds
- BM-3357 - Don't display Deployables on Release Overview if Application has no Deployables
- BM-3358 - FIX: Drag/dropping a General block in the plan editor is improperly sized
- BM-3348 - FIX: Placeholder text for $WorkingDirectory doesn't show up when editing an operation
- BM-3354 - FIX: Plan editor should say "call module" instead of "call template"
- BM-3346 - Add support for OtterScript "throw" expressions
- BM-3347 - FIX: Manual license key entry value is ignored in traditional installer
- BM-3288 - FIX: Possible DB deadlock errors in the PipelineStageValidatorRunner
- BM-3291 - FIX: Web crawlers can cause superfluous errors to be written to the diagnostic center
- BM-3345 - Invoke-Operation throws exception
- BM-3343 - Limit the number of active releases listed on the Application Overview page
- BM-3341 - Move "Active Releases" as the first item in the Application Overview page
- BM-3323 - Add "Executions" on Promotion/Deployment Details Modal Page
- BM-3326 - Add $ApplicationGroupName variable function
- BM-3331 - Add release template as an option for Create-Release and Ensure-Release operations
- BM-3336 - Allow variable value renderers to be supplied on the Application Settings page
- BM-3330 - Changes to Build & Release Management API release endpoints (support deployables, auto-increment release number)
- BM-3339 - Check that artifact uploads are .zip files.
- BM-3324 - Clarify text on the No Active Releases dialog
- BM-3328 - Create new application should generate a build stage
- BM-3337 - Create-Artifact does not work with $WorkingDirectory
- BM-3322 - Delete approval icon is displayed even without manage pipeline permissions
- BM-3320 - FIX: Extensions that use properties of Inedo.SDK fail when run on agents.
- BM-3332 - FIX: Pipeline gets stuck in a bad state if a variable function is used in an approval variable
- BM-3327 - FIX: Possible race condition with logging and multiple concurrent executions
- BM-3325 - FIX: ReleaseNumberPart function not working for 3 part releases
- BM-3333 - FIX: Unhelpful error message for unhandled exception in repository monitors
- BM-3338 - Improve extension installation experience
- BM-3321 - Pipeline Deployment Window overrides Scheduled Timing
- BM-3334 - Pipeline screen change to differentiate stages and targets..
- BM-3329 - Show latest release and deployments on the application overview page
- BM-3340 - Update homepage to make it more obvious when there are no privileges granted, add Slack workspace to help and support section
- BM-3303 - $ReleaseNumberPart function returns the last 2 numbers in a 4-part version number instead of just the 3rd
- BM-3297 - FIX: [Traditional Installer] Parse error reading non-semver2 version number from registry prevents currently installed version from being detected
- BM-3301 - FIX: API keys that impersonate a user without privileges results in a 500
- BM-3293 - FIX: Auto-generated help documentation still refers to PackageNumber instead of BuildNumber
- BM-3290 - FIX: Calendar "create" links still appear for anonymous user
- BM-3289 - FIX: Clearing values in an issue source does not persist
- BM-3306 - FIX: Deleting Git webhooks can result in a reference constraint error
- BM-3298 - FIX: Export application to feed can cause stalled execution
- BM-3308 - FIX: GitHubHookData.cs is referencing GitLabRepository and should probably be referencing GitHubRepository instead
- BM-3292 - FIX: If there are no repository monitors, the help link to "install the Git extension" opens the extensions page in the modal
- BM-3315 - FIX: Improperly packaged extensions can cause intermittent type resolution and serialization failures
- BM-3304 - FIX: Login page exceptions do not display as an error message on the screen
- BM-3307 - FIX: packageId and packageNumber arguments are not backwards compatible when hitting Build & Release Deployment API endpoints if specified in content body
- BM-3295 - FIX: Plan version history for modules renders a broken link
- BM-3305 - FIX: Recoverable exceptions during command deserialization should not cause dropped connections
- BM-3317 - FIX: Some webhook and repository monitor variables are not populated
- BM-3309 - FIX: The DeployBuild operation seems to be using the PipelineNameSuggestionProvider although this operation actually wants pipeline stage names.
- BM-3299 - FIX: Variable cascade behavior for configuration files does not handle cascaded configuration variables defined at multiple scopes
- BM-3319 - FIX: Variables of the same name at different levels in nested environments may not resolve correctly at runtime
- BM-3300 - FIX: Warning text is invalid on issues page when built-in issues are disabled
- BM-3302 - Reject build button coloring should be orange instead of blue
- BM-3318 - Remove nonexistent support methods from error pages
- BM-3294 - Retention policy logged errors should not include the stack trace in the message
- BM-3313 - Update InedoLib to v535 (fixes autocomplete dropdowns in plan editor, improves extension loader logging, fixes agent command deserialization crashes)
- BM-3264 - Add "Ensure-Release" operation
- BM-3286 - Add "quick refresh" option to issues page for an application
- BM-3275 - Add ability to edit roles on server page
- BM-3270 - Add CI Badge API
- BM-3260 - Add duration to log scope headers in execution log viewer
- BM-3284 - Add Loupe integration (disabled by default)
- BM-3287 - Add option to disable connection to inedo.com/rss
- BM-3277 - Add option to filter servers by Inactive status on servers page
- BM-3278 - Add PipelineStageName Variable Function
- BM-3249 - Add Restart-Server operation to BuildMaster
- BM-3274 - Add Variable Value Renderers
- BM-3236 - Allow servers to be filtered by "no role" and "no environment"
- BM-3262 - Change "Automatically deploy to [first] stage" to use the term "advance" instead of "deploy"
- BM-3276 - Display roles on server overview page
- BM-3272 - FIX: Anonymous user should not be able to create calendars
- BM-3282 - FIX: ArgumentException raised when trying to use map variables as output parameters for operations
- BM-3267 - FIX: Create-Release operation does not handle ReleaseName property correctly
- BM-3259 - FIX: Database error when creating or updating build variables through the API
- BM-3280 - FIX: Do not attempt to run an execution completed/failed/cancel event listener unless the execution is actually a "Build/Deployment" type
- BM-3281 - FIX: Environment-scoped variables in configuration file deployment do not inherit ancestor values
- BM-3279 - FIX: Execution failure events are not triggered
- BM-3273 - FIX: Issue sources page table missing empty message
- BM-3268 - FIX: Proxy configuration page should be displayed as modal
- BM-3271 - FIX: Release Template list variables with multiple values act like strings when fewer than two values are selected.
- BM-3285 - FIX: Set-ReleaseVariable truncates values
- BM-3261 - FIX: Variable template validation issue causing strange behavior when switching from JSON mode to editor mode
- BM-3269 - Improve script and text template asset editor
- BM-3257 - Rename "Release Packages" to "Builds"
- BM-3266 - Update InedoLib to v532 (fixes modal window sizing)
BuildMaster 6.0 - Supported
- BM-3258 - FIX: (regression) API keys no longer work without a user specified
- BM-3265 - FIX: Possible race condition in extension initialization of web application
- BM-3252 - Add Set-ConfigurationVariable operation
- BM-3202 - Allow API keys to impersonate specified users and implement associated privilege checks with API endpoints
- BM-3250 - Change PipelineStageName to PipelineStageNames on Release Template Deployment Variables
- BM-3254 - FIX: Do not assign a named user license if the browsing user has no privileges in the system
- BM-3245 - FIX: Exception when deploying an XSLT-based configuration file
- BM-3253 - FIX: Release Template variable descriptions are not displayed on the Create Release page
- BM-3255 - Log warning at start of execution if core extensions aren't loaded
- BM-3237 - Add LogMessages_CreateMessage to public native API
- BM-3191 - Add the concept of execution priority
- BM-3243 - Agent hostname information should not be displayed on server page unless user has Manage Infrastructure permission
- BM-3224 - Change the execution progress bar to yellow or red if the execution is currently in a warning or failing state.
- BM-3241 - Deploying a configuration file from the web UI now pre-fills the directory and filename with the last value used per server and configuration file
- BM-3235 - Display user that canceled a deployment
- BM-3228 - FIX: Change script history schema update fails on installation in some locales
- BM-3227 - FIX: Deploy Package endpoint does not update variables if the package has already been promoted to that stage
- BM-3229 - FIX: Deployment timeline on Build Overview page ignores environment association for its display logic
- BM-3244 - FIX: Extracting configuration values via the SDK.GetConfigurationValue() method does not return default values
- BM-3240 - FIX: Plan editor crashes when attempting to pull source paths from TFS
- BM-3226 - FIX: Post-deployment event listeners are required to support all relevant events
- BM-3230 - FIX: Some invalid requests return a HTML error page and log an unhandled exception
- BM-3242 - FIX: Users with no privileges in the system at all should not be able to access the "view-only" pages
- BM-3223 - Italicize operations that are waiting for an external resource to become available
- BM-3231 - Limit number of release panels on the Application Overview page
- BM-3233 - Show release pipeline color on system overview page
- BM-3221 - Add $IncrementReleaseNumber variable function.
- BM-3216 - Display the agent version information on the servers page
- BM-3219 - FIX: $PackageNumber logic for "furthest" and "latest" is swapped.
- BM-3220 - FIX: Do not include hidden system files in artifact creation
- BM-3222 - FIX: Export application may produce improperly-formatted JSON [regression]
- BM-3218 - FIX: Non-shared configuration fallback still logs "no encryption key" message to Message Center
- BM-3217 - New installations should set IIS AppPool configuration to use Classic pipeline
- BM-3214 - Retry loading assemblies in PowerShell agent host if any of them are locked
- BM-3189 - FIX: Bulk variable editor is not visible for applications if infrastructure sync is enabled
- BM-3213 - FIX: Legacy agents do not update correctly [6.0.7 regression]
- BM-3212 - FIX: Purge release does not delete release notes from the database
- BM-3194 - Improve performance on pages related to releases or deployables.
- BM-3186 - Add approval list to pipeline stage deployment dialog
- BM-3201 - Allow read-only access to release packages from releases with deleted pipelines
- BM-3204 - FIX: Application Overview is showing non-active package notes
- BM-3207 - FIX: Email event listeners do not send emails to the default address if there are no explicitly specified addresses.
- BM-3209 - FIX: Exporting an application fails if more than one release or release template references the same global pipeline
- BM-3203 - FIX: Odd CSS for server role buttons
- BM-3211 - FIX: Publish Event Details event listener editor does not save selected event types
- BM-3210 - FIX: Release package trigger variables are incorrectly created using the name of the trigger instead of the name of the variable.
- BM-3208 - FIX: Selecting an autocomplete result from a release template variable does not update the value
- BM-3206 - Remove uses of legacy configuration database calls
- BM-3199 - FIX: Create-ReleaseNote does not store the promotion ID, causing notes to always be release-scoped
- BM-3198 - FIX: Release page can crash (beta 4 regression)
- BM-3200 - See the Upgrade Notes for more information: https://inedo.com/support/kb/1156/buildmaster-60-upgrade-notes
- BM-3183 - Add /api/releases/restore endpoint
- BM-3197 - Add Plan Modifed Event Listener
- BM-3184 - FIX: Additional headers in OtterScript other than AH:Description are lost when switching to the visual editor
- BM-3190 - FIX: Bulk variable editor expects variable names in the wrong format when saving
- BM-3182 - FIX: editing a release template that refers to an inactive pipeline changes the pipeline
- BM-3187 - FIX: Message center should ignore "a task was canceled" exception from the Issue Summary control
- BM-3192 - FIX: Release/Package Notes
- BM-3185 - FIX: some deadlock errors may not cause the build overview page to retry
- BM-3195 - FIX: Unnecessary logging for issues panel on release overview page
- BM-3196 - FIX: Various permissions issues related to anonymous users in Free Edition
- BM-3193 - Implement anonymous user behavior to match v6.0 documentation
- BM-3179 - FIX: $ServerName may not resolve in some cases
- BM-3180 - FIX: Possible undisposed database connections if issue source refresh takes longer than expected
- BM-3178 - FIX: server list variable source broken in 6.0 if created in 5.x
- BM-3176 - FIX: Users with no modification privilege cannot compare plans or view text templates
- BM-3163 - Remove multiple license key support and determine single key based on the last added key that has been activated
- BM-3164 - Rename "Message Center" to "Diagnostic Center" and allow the log message verbosity to be configured on that page
- BM-3181 - Upgrade Inedo.ExecutionEngine to v64
- BM-3177 - Various UI/UX tweaks
- BM-3174 - Add DoNotShare property to Acquire-Server operation
- BM-3172 - FIX: "for server" with nonexistent server gives unhelpful error message if Agents.EnforceServerRestrictions is enabled
- BM-3173 - FIX: Acquire Server can fail unexpectedly if verbose logging is enabled
- BM-3175 - FIX: Application export includes global plans as application plans
- BM-3119 - FIX: Deploy-Artifact for Source Application without Deployable Fails
- BM-3167 - FIX: dynamic list variable sources broken in 5.x to 6.0 upgrade
- BM-3170 - FIX: live execution output does not check privileges for debug logs
- BM-3166 - Redirect to application issue pages for single-application issue sources
- BM-3165 - Set-ReleaseVariable should support list and map values
- BM-3147 - Add "Require Issues Closed" Automated Gate
- BM-3162 - Add variable functions: @ApplicationReleases, @ReleasePackages, ReleaseVariable, PackageVariable
- BM-3149 - Allow Scheduled Deployments from Release and Package API
- BM-3120 - Application names in the application dropdown menu wrap on underscores in addition to hyphens
- BM-3132 - Clarify behavior on IssueTrackerPromotionRequirement
- BM-3151 - FIX: Deleting event listeners requires admin privileges even for the current user's event listeners
- BM-3152 - FIX: Event listener owner is not read by the editor which may result in inability to edit unless the user is an administrator
- BM-3159 - FIX: exception thrown when viewing test results for an execution with no tests
- BM-3154 - FIX: JSON variable editor should validate variable names when updated instead of at run time
- BM-3158 - FIX: Occasional redirect to an error page at the end of an execution instead of the package overview
- BM-3153 - FIX: Remove "Server licenses available" Restriction from UI
- BM-3155 - FIX: ServersInRole function can return inactive servers
- BM-3157 - FIX: SSH processes are not interrupted by cancellation of an execution
- BM-3161 - Improve type load error for legacy types
- BM-3150 - Optimize stored procedure for searching for variables by application group
- BM-3126 - Reduce execution log load time for long execution logs
- BM-3160 - Update logo on notification emails
- BM-3122 - Add "Ignore Read-only" option on Deploy Artifact Operation
- BM-3146 - Add link to toggle non-recommended extensions from Extensions Overview page
- BM-3139 - Deprecate Change Control Feature as Legacy Feature
- BM-3145 - FIX: BuildMaster API initialization fails breaking existing API calls
- BM-3144 - FIX: Execution log links should not default to legacy execution page
- BM-3143 - FIX: NullReferenceException on execution details page if original deployment plan is missing or deleted
- BM-3138 - Add "Restrict to environment use" option to resource credentials
- BM-3129 - Add "Restrict Use to Environment" checkbox on Database Connections
- BM-3127 - Add Assets tabs under (global) Plans
- BM-3128 - Add help text to Server field on Database Connection
- BM-3133 - Add properties to Create-ReleaseNote Operation
- BM-3112 - Added /api/releases/cancel endpoint
- BM-3137 - Clarify usage of $CredentialProperty
- BM-3136 - Deprecate Issue Tracker Provider Event Listeners
- BM-3123 - Deprecate/hide date/time-based promotion requirement (replaced with deployment windows feature)
- BM-3142 - FIX: An pipeline with an empty name can be created if a cloned application does not have any application-specific pipelines
- BM-3130 - FIX: BuildMaster uninstaller does not remove services on some systems
- BM-3125 - FIX: Execution details page can generate a non-deterministic JavaScript error if there are no log scopes created for an execution
- BM-3131 - FIX: Global issue sources page crashes if issue source cannot be deserialized
- BM-3141 - FIX: Releases created from a template may use the wrong pipeline if another application has a pipeline with the same name
- BM-3116 - Installer: Change Default Web Site Port to 8622, SQL Express Instance to "INEDO"
- BM-3124 - Pipeline editor: rename "Gate" heading to "Approvals"
- BM-3135 - Remove "Create New URL Trigger" button from the Release Package Triggers page
- BM-3140 - Upgrade Inedo.Execution Engine to fix IEE-9
BuildMaster 5.8 - Supported
- BM-3110 - Added the ability to filter releases by pipeline and deployable
- BM-3118 - Display line break for release note
- BM-3111 - FIX: Build schedules show legacy variable editor even if there are no legacy variables
- BM-3121 - FIX: Deploy configuration file page path picker fails when a legacy server group is targeted
- BM-3113 - FIX: Infrastructure sync fails with a database error if any variables changed
- BM-3115 - FIX: Legacy build schedules cannot create variables
- BM-3075 - FIX: Overriding failed promotion status for final stage that would have normally caused the package to be deployed generates a 500 error
- BM-3117 - InedoLib: Update from 507 to 520
- BM-3114 - New SSH agent implementation
- BM-3103 - FIX: Active Releases on overview page can overflow if application/release names are long
- BM-3108 - FIX: Deploying XSLT configuration files uses XslTransform instead of XslCompiledTransform
- BM-3107 - FIX: FIX: Event listeners with RequireManageAllPrivileges could be created by unprivileged users in some cases
- BM-3109 - FIX: If deploying using the Release & Deployment API, the release package should not be promoted if it was already promoted
- BM-3101 - FIX: Open redirect handling (ensure local address before HTTP redirect)
- BM-3100 - FIX: Possible XSS vulnerabilities
- BM-3098 - FIX: Release list on dashboard does not update unless the number of active releases changes
- BM-3104 - FIX: Release package triggers do not activate the day they are created, even if they are scheduled for a future time of day
- BM-3102 - FIX: Renaming a template plan does not update the web interface
- BM-3099 - FIX: server roles containing servers in deleted environments are not visible
- BM-3105 - FIX: Soft-deleted plans can be referenced by pipeline stages
- BM-3096 - InedoSsh: Upgrade from 2.0.8 to 2.0.9
- BM-3081 - Add @DatabaseConnectionsInEnvironment variable function
- BM-3093 - FIX: Duplicate environment message appears as an asterisk with no text
- BM-3082 - FIX: Editing a plan template's name results in an error
- BM-3091 - FIX: Environments dropdown should pre-populate with autocompletion values on extension configuration variable page
- BM-3087 - FIX: Execution overview does not show cancelled executions
- BM-3079 - FIX: Installation issue when default database server collation is case-sensitive
- BM-3092 - FIX: Manual artifact upload page requires Admin_ConfigureBuildMaster privileges instead of ReleasePackages_Manage at the application level
- BM-3085 - FIX: Notification bar ignores environment scoped privileges when displaying "Deployment in progress..."
- BM-3095 - FIX: Recurring scheduled build should not fire immediately if set in the future
- BM-3078 - FIX: Variable column on Pipeline can overlap steps
- BM-3020 - FIX: View Details button for Issue Source Refresh execution displays a broken page
- BM-3084 - BuildMaster v5.8 Beta - see http://inedo.com/support/kb/1149 for more information
BuildMaster 5.7 - Supported
- BM-3004 - Add Invoke-Operation Operation
- BM-3072 - FIX: ExecutionCompletedEventListener can deadlock attempting to get the list of deployables for the release
- BM-3073 - FIX: infrastructure import dry run fails when an environment would be created
- BM-3074 - FIX: NullReferenceException in Deploy-Package operation
- BM-3009 - FIX: Race condition with artifact retention policy "purge orphaned artifacts" option; new artifacts can be deleted if the file happens to be enumerated before the database record is added
- BM-3070 - FIX: Template plan visual editor makes default-empty arguments non-optional
- BM-3028 - Improve default text for approval gate
- BM-3019 - Release and Package variables table overlaps the artifacts table if a variable value is long enough without whitespace
- BM-3058 - Add EnumerateDependents permission to INEDOBMSVC
- BM-3066 - FIX: Compare artifacts report does not show modified files
- BM-3068 - FIX: Configuration file difference preview popup is not scrollable in Internet Explorer 11
- BM-3061 - FIX: executions containing async blocks may report success even if they fail
- BM-3069 - FIX: Include masking of "dir\**" incorrectly matches "dir.txt" even if dir.txt is not in a subdirectory indicated by the **
- BM-3060 - FIX: Infrastructure API doesn't update agent configurations
- BM-3035 - FIX: Manual configuration file deployment ignores variable functions
- BM-3057 - FIX: Pipelines record the wrong username for edits
- BM-3067 - FIX: Release and package API requires application ID even when release ID is specified
- BM-3063 - FIX: Release package retention policy ignores pipeline filter
- BM-3059 - FIX: View Pipeline page should require Application_View privilege, and should hide "edit" links if Pipelines_Manage is restricted instead of allowing them to be clicked and showing an error message
- BM-3062 - Improve error messages when cloning or renaming an application results in a duplicate application name
- BM-3049 - License name changes
- BM-3056 - Deployment Windows
- BM-3045 - FIX: Compare directories reporting operation diffs inaccessible on Windows agents
- BM-3015 - FIX: Error when a non-administrator visits the Create New Event Listener page
- BM-3051 - FIX: Performance regression when deploying configuration files with many undefined variables
- BM-3048 - FIX: Template plan editor creates input parameters when "add output parameter" is clicked
- BM-3047 - FIX: Template plans fail to save if arguments are added but not given a name
- BM-3044 - Require Deploy_Scripts in addition to Manage_Application task for editing database connections in application
- BM-3037 - Add Acquire/Release Server operations for OtterScript implementation of server pools
- BM-3024 - Add warning if only "furthest" or "latest" is specified for Deploy-Artifact, but no Release Number or Application Name
- BM-3033 - Clarify missing "for server" error message during deployments that require server context
- BM-3015 - FIX: Error when a non-administrator visits the Create New Event Listener page
- BM-3038 - FIX: Last character of global shell script name not shown on overview page
- BM-3017 - FIX: Pipeline variables duplicate explicitly provided variable type prefix
- BM-3016 - FIX: Renaming pipeline variables creates duplicates
- BM-3036 - Show configuration file instance notes on the All Configuration File Versions page
- BM-3039 - v5.7 - Calendars Feature
BuildMaster 5.6 - Supported
- BM-3014 - FIX: Legacy template variables are not considered in legacy plans
- BM-3002 - FIX: Package re-deployment ignores environment-specific permissions
- BM-3012 - FIX: Retention policies can run outside of the specified time span
- BM-3003 - FIX: Sync Legacy Issues gives non-helpful error messages when it fails
- BM-2374 - Add @ConfigurationFiles and @ConfigurationFileInstances functions
- BM-2384 - Add API endpoint to create a release from a release template
- BM-2386 - Add API endpoint to reject release packages
- BM-2382 - Add clearer details to error message (and remove stack trace) when an operation property value fails to map correctly
- BM-2393 - Add Compare Directory Report Operation
- BM-2383 - Add deployable name to release configuration file list if associated with a deployable
- BM-2376 - Allow Deploy Artifact operation to clear target when "TransferAll" is true, and add warning on Deploy-Artifact if TransferAll and DeployAsZip are both set
- BM-2395 - Display pipeline name in addition to next stage name on the My Approvals page
- BM-2370 - FIX: "System.InvalidCastException" attempting to run Approval Required event listener in the service
- BM-2373 - FIX: Compare-Artifacts Operation uses legacy artifact path
- BM-2371 - FIX: Create package link on packages page does not pre-fill release template package variables
- BM-2391 - FIX: DB changescripter executable should return nonzero exit code when a change script fails
- BM-2385 - FIX: Error during manual infrastructure import from Otter
- BM-2369 - FIX: Pipeline variables incorrectly override variables defined in a release template
- BM-2381 - FIX: Role not set in execution when servers are selected by role in a pipeline stage
- BM-2389 - FIX: Template properties button may not show up in plan editor
- BM-2392 - FIX: Variable bulk edit for releases and release packages checks for Admin_ConfigureBuildMaster task instead of Releases_Manage
- BM-2388 - FIX:Variables from ancestors of the current application group are inaccessible
- BM-2377 - Increase visibility of "run now" button for retention policies page
- BM-2327 - Add CC email addresses property to Manual Operation
- BM-2364 - Add operation converter for "Attach Directory Report" action
- BM-2365 - Add options to view and download logs on the Execution Details page
- BM-2363 - Allow release package triggers to be filtered by a specific release
- BM-2366 - FIX: Deleting application variables does not immediately update in the UI and requires an unnecessary refresh
- BM-2362 - FIX: Legacy style variables may be erroneously replaced in configuration files
- BM-2367 - FIX: Potential for database connection leaks from some operation suggestion providers
- BM-2359 - FIX: Regression from 5.6.7 (BM-2351) causes errors when attempting to edit variables as JSON
- BM-2361 - FIX: Source control path selector doesn't work in legacy plans
- BM-2353 - Add "Deploy all files, regardless of whether they changed" checkbox on deploy artifact operation under advanced options
- BM-2348 - Change max request length in web.config to allow for large manual artifact uploads
- BM-2354 - FIX: "User must change password" option does not display a clear error message if the newly entered password is not different from the old password
- BM-2347 - FIX: Config Files in Legacy Plans with Legacy Agents May Not Replace All Variables
- BM-2340 - FIX: Create Release API will ignore supplied release name
- BM-2350 - FIX: Execution In Progress Checks for Admin_ConfigureBuildMaster instead of Admin_ManageApplications and Issues_Manage
- BM-2357 - FIX: Incorrect pipeline displayed on edit release page when there are active release packages preventing modification of the pipeline
- BM-2351 - FIX: JSON Variable Editor Requires Admin_ConfigureBuildMaster instead of more granular privileges
- BM-2342 - FIX: Long names in pipeline variables should be overflow: hidden
- BM-2349 - FIX: Release Deployed Event Listener May Cause Variable Replacement Error
- BM-2352 - FIX: Show % instead of @ for map types on Operations Listing page
- BM-2341 - FIX: Unable to delete configuration profile that cannot be deserialized
- BM-2355 - Indicate on the Promote Package page when there is a scheduled promotion and if there is, what needs to happen for it to occur
- BM-2330 - Optimize CanPromoteBuild::Builds_GetPromotions to reduce deadlocks
- BM-2358 - Support enforcement of server/environment restrictions if enabled in OtterScript plans
- BM-2345 - Add option to use alternate SSH client
- BM-2344 - FIX: Script asset arguments to PsEnsure passed in with a map are not parsed correctly
- BM-2343 - FIX: Some legacy config file variables may not get replaced (regression caused by BM-2317)
- BM-2329 - Change color for "Override Deployment Status button to orange
- BM-2321 - FIX: "Cancel Scheduled Execution" button does not cancel the execution immediately if the execution is scheduled in the future
- BM-2328 - FIX: Cannot set user or group for change controls
- BM-2338 - FIX: Custom implementations of ICustomArgumentMapper do not have the OutputArguments property applied in some cases
- BM-2333 - FIX: Deploy Multiple Configuration Files legacy action editor displays "Object reference not set..." exception
- BM-2320 - FIX: Direct links to Execution Details for legacy plan executions should automatically redirect to the legacy execution details page
- BM-2336 - FIX: Dropdown is not pre-populated when a default value is selected for a dynamic list variable
- BM-2332 - FIX: Error written to error log when notification bar shows "Execution in progress" for non-deployment executions
- BM-2322 - FIX: Execution In Progress Redirects using Release Name instead of Number
- BM-2334 - FIX: JSON API does not parse POST body input as JSON unless content type is explicitly "application/json"
- BM-2324 - FIX: Manual action responsible principal input is hidden
- BM-2337 - FIX: Namespaces are not generated when multiple operations with the same script aliases are written when switching from visual mode in the plan editor
- BM-2335 - FIX: Server list variable source incorrectly requires servers to be associated with an environment in order to appear in the list even when "any environment" is configured
- BM-2331 - FIX: Use of $Eval on an operation property uses an incorrect variable context
- BM-2325 - Restore the "Re-Execute from Last Failed" button for legacy plans on "Execution In Progress" page
- BM-2318 - Add option to Create Artifact operation to suppress "0 files captured" warning
- BM-2314 - Display "AppName::DeployableName" in systems variable overview
- BM-2315 - FIX: Invalid Promotion Requirement Causes Pipelines to be Uneditable
- BM-2319 - FIX: Source control picker may generate a JavaScript error when application ID is not in scope
- BM-2317 - FIX: Variable Function Evaluation in Configuration Files May not Be Replaced
- BM-2316 - Use Stage Name instead of Environment Name on Package Deployments
- BM-2313 - FIX: Cannot add system-level event listeners when pipeline stage names contain a comma
- BM-2312 - FIX: Clicking the servers link on the roles page should filter the list of servers by that role and include a dropdown to change the role
- BM-2311 - FIX: Deployment execution completed event listener does not fire after deployments to pipeline stages that utilize a legacy plan
- BM-2309 - FIX: Infrastructure Sync Does Not Consider "Active/Inactive" Drift
- BM-2307 - FIX: Legacy Transfer Files Action to a Server Group may Yield Deployment Errors When Initializing Servers
- BM-2305 - FIX: MultiDomainActiveDirectory throws COMEXception if a domains in the forest is not accessible
- BM-2295 - FIX: Operation arguments that accept a map generate a compilation error if one of the values in the map is an empty string
- BM-2310 - FIX: SOAP API should generate string types for parameters of YNIndicator type
- BM-2303 - FIX: A context iteration block that loops over @ServersInRole gets converted to "foreach role" when switching from text mode to visual mode and back to text mode
- BM-2300 - FIX: Cannot update or delete extensions from Admin Extensions page if the extension has a space in the name
- BM-2301 - FIX: Extension configuration variables page does not filter by extension name correctly
- BM-2302 - FIX: Selecting "do not execute" may be ignored when deploying to a pipeline stage with multiple targets
- BM-2304 - FIX: User directory descriptions display the full name of the directory instead of the custom description
- BM-2299 - FIX: Build importer executions do not immediately get picked up by the PlanExecuter even though they can never be executed in the future
- BM-2298 - FIX: Deployments may stay in AwaitingExecution status if they are not triggered through the UI on initial deployment
- BM-2272 - Add Last modified date and pipeline color to the Pipeline Overview page
- BM-2291 - Allow pipeline targets to run either in parallel or sequentially
- BM-2294 - Display the server or role of the pipeline stage target on the package overview page deployment list
- BM-2275 - Don't display Issue, Source, or Database Operations unless appropriate Providers have been configured
- BM-2289 - FIX - Output variable values only persist within the current and descendant scopes... not sibling scopes
- BM-2288 - FIX Environment Count on Server Roles Page
- BM-2290 - FIX: Add a constraint to prevent release package numbers from being set to an empty string
- BM-2274 - FIX: Better handling for custom predicate when converting legacy plans
- BM-2281 - FIX: Configuration file deployment may not resolve legacy server variables
- BM-2283 - FIX: Configuration variables May Appear as Multi-scoped when only a single scope
- BM-2293 - FIX: Deployment status should reflect the aggregate result all deployments when multiple targets are used instead of just the result of a single deployment
- BM-2282 - FIX: Editor for Call Template statement displays "Object reference not set"... error
- BM-2279 - FIX: Error/warning box scrolls with text content of plan editor in code mode
- BM-2273 - FIX: Event listener pipeline stage filters do not populate the auto-complete correctly
- BM-2276 - FIX: Infrastructure Management API May throw "Invalid Entity Type"
- BM-2278 - FIX: Map-type variable evaluation causes exception using MapItem function
- BM-2297 - FIX: Native JSON API overview page displays a content decoding error
- BM-2285 - FIX: Re-execute/deploy page does not list release template deployment variables
- BM-2277 - FIX: Release Templates with Duplicate Pipeline Variables Cause Duplicate Key Error
- BM-2280 - FIX: Release variable names may be hidden if user does not have Manage Variables permissions
- BM-2296 - FIX: Retention Policy may not select proper pipeline id in filering
- BM-2287 - FIX: ServerPage Displays Legacy Name for SSH Agent URL
BuildMaster 5.5 - Supported
- BM-2271 - FIX: Don't automatically preview reports created from the Create Report from Directory Action
- BM-2266 - FIX: FK Error During Build/Package Purge May Occur With Legacy Executions
- BM-2267 - FIX: Increase visibility of Approvals on Previous Promotions
- BM-2269 - FIX: ManualOperation may raises exception looking up user in directory
- BM-2270 - FIX: PlanEditor: Saving PSCall-based Operation may yield error in visual editor
- BM-2262 - FIX: Deploy artifact action fails when the target directory is specified with a trailing slash
- BM-2264 - Prevent Immediate Execution of new Schedule Trigger
- BM-2261 - FIX: Variable Resolver May Yield Deadlock with High Concurency
- BM-2255 - Add $ArtifactPath(artifactName, [appName], [relNum], [pkgNum]) function
- BM-2248 - FIX: Deployables list does not refresh after deleting a deployable
- BM-2249 - FIX: Error downloading changescripter tool when there is only one DB connection type
- BM-2257 - FIX: Variables API May Return Invalid Entity for release Variables
- BM-2259 - PlanEditor: Add "Iteration type" to simplify ServersInRole and Range usage
- BM-2256 - Rebuild Built-in Task Definitions
- BM-2258 - SDK: Obsolete PromotionRequirementBase/EditorBase in favor of PromotionRequirement/Editor
- BM-2260 - See the Upgrade Notes for v5.5 page for more information: http://inedo.com/support/kb/1135
- BM-2254 - Set Web, Service RestartRequired immediately after attempting to install extension
BuildMaster 5.4 - Supported
- BM-2246 - FIX: Build Output Reports May Throw Error When Incorrect Casing is used in Index File
- BM-2247 - FIX: Configuration Variables with Nested Maps Do Not Process Properly
- BM-2252 - FIX: Deployment/Prompted Variables May Not Appear for Appropriate Pipeline Stage
- BM-2250 - FIX: PlanEditor error when adding template variables
- BM-2251 - FIX: PlanEditor may not display all powershell script assets available
- BM-2253 - FIX: Release Template JSON View May not Save
- BM-2242 - FIX: Cache UserConfig Values to Aide Viewing of Extremly Large LogFiles
- BM-2236 - FIX: Cannot add legacy scripts to legacy plans in some cases
- BM-2240 - FIX: DB update tool can fail on mono with assembly load error
- BM-2241 - FIX: Deployment Template Variables May Not Be Displayed on all Deployments
- BM-2237 - FIX: Display Friendly Message When Permission Denied to Access PowerShell Assets Page
- BM-2239 - FIX: Error downloading changescripter tool when there is only one DB connection type
- BM-2238 - FIX: Non-legacy Configuration Variables May Not Get Cloned During Clone Application
- BM-2235 - FIX: Paths on Linux servers are sometimes resolved using Windows directory separators
- BM-2245 - Include Pipeline Name Auto-complete in Deployment Variables for Release Template
- BM-2244 - Increase visibility of deployables on SQL script asset list
- BM-2208 - Add DependentUpon_Execution_Id to Executions table to enable chained deployments
- BM-2228 - Add note about legacy variable templates
- BM-2234 - Deprecate BuildMaster Admin Tool in favor of running service interactively
- BM-2233 - FIX: [5.3.8 regression] Legacy agent updates can leave some agents in an unusable state
- BM-2224 - FIX: Add failure logging to InitializeRemoteConfiguration for legacy actions
- BM-2227 - FIX: Force should be required if trying to deploy to the furthest stage in a pipeline after a deployment failure in the previous stage
- BM-2232 - FIX: Infrastructure sync may report 401 Windows integrated auth
- BM-2226 - FIX: Plan editor "Disabled" setting clears some execution options
- BM-2222 - FIX: Promotion details page should not require ReleasePackages_ViewDeploymentLogs privilege
- BM-2229 - FIX: Purge execution log retention policies do not always purge non-legacy execution logs
- BM-2230 - FIX: Runtime variables inside of configuration file template instances may not be replaced
- BM-2225 - FIX: Tag operation has source/to parameters in wrong order
- BM-2068 - Improve error message for when duplicate artifact name is created during a build
- BM-2215 - Remove Applications.AllowMultipleActiveReleases_Indicator column
- BM-2199 - SDK: Deprecate SourceControlFileFolderPicker in favor of ScmBrowserTextBox and FileBrowserTextBox
- BM-2198 - SDK: Deprecate Util.Agents in favor of BuildMasterAgent factory methods
- BM-2214 - Use internal IDs for artifact paths instead of build and release numbers
BuildMaster 5.3 - Beta
- BM-2220 - 5.4 Preview: Agentless Windows servers
- BM-2210 - Add "Create Auto-Deploying Extension Application" page under Extensions
- BM-2216 - Add better visual indicator for multi-scoped tasks and privileges
- BM-2218 - Add SCM Tag Operation
- BM-2212 - Allow user-defined time zones
- BM-2211 - Email template formatting tweaks for Outlook
- BM-2219 - FIX: Deploy Artifact operation errors when DoNotClearTargetDirectory is false
- BM-2217 - FIX: Error with WriteCommandHelp on ExecuteClientCommand legacy action
- BM-2221 - FIX: Multi-scoped environment variables may return variables out of scope
- BM-2213 - FIX: Source control path picker should escape $ characters in paths
- BM-2200 - Add Artifact File Browser
- BM-2117 - Add File/Directory Browser For Disk Paths
- BM-2206 - Add Legacy Action Importer for SetVariableFromFileAction
- BM-2201 - Add Server Usage Not to Debug Logs for Operations
- BM-2197 - FIX: All Applications Page should display environments by Application, not Application Group
- BM-2209 - FIX: Coercion Errors from TimeSpan Properties
- BM-2196 - FIX: Create Release Package Operation Should Not Require ReleaseNumber
- BM-2195 - FIX: Filter on Servers Overview Page May Cause Error for Switching Enviroments
- BM-2202 - FIX: Manual Operation may write an error with full stack trace to the execution log if the SendEmail property is true
- BM-2207 - FIX: Pipeline auto-create release option should assume the release template of the previously deployed release
- BM-2203 - Operations with a Credentials property should allow individual mapped properties to be overridden at the operation level
- BM-2194 - FIX: Legacy Build Importers May Cause Issue with All Applications Page
- BM-2188 - Add Convert to Inedo Agent Option for IIS-based Legacy Agents
- BM-2118 - All Applications Page: Show Only Environments Used in Pipelines in Application Group
- BM-2190 - Allow changing the release template after the release is created
- BM-2185 - FIX: Create-ReleasePackage Operation May Not Set Package Variables
- BM-2186 - FIX: Deploy Artifact action should include empty directories contained within the artifact
- BM-2192 - FIX: Do not allow periods to be used in template names
- BM-2183 - FIX: PsCall output arguments may not bind correctly depending on the type of the target
- BM-2184 - FIX: Release template variable checkboxes should coalesce description and name
- BM-2191 - FIX: Target date displayed on Release Details should display a short date and does not use the correct timezone
- BM-2193 - FIX: Variable predicate for legacy plans does not evaluate v5.3 cascaded variables correctly
- BM-2189 - Ignore spaces in extension names when comparing results found from the Inedo Den to determine latest version
- BM-2168 - Add "Legacy" Note to Server Groups
- BM-2172 - Add XSLT configuration file template type where the XSL stylesheet is the template, and the XML documents are the instances
- BM-2166 - FIX: Always treat variables that do not start with map/list specifier followed by an opening parenthesis [i.e. %( or @( ] or grave apostrophe as a scalar value
- BM-2173 - FIX: Change Controls Performed automated gate approval cannot be serialized properly
- BM-2176 - FIX: Create retention policy time parsing generates an error
- BM-2178 - FIX: Deleting application groups or retention policies may result in JavaScript errors in certain browsers
- BM-2175 - FIX: Editing an anonymous legacy deployment plan that is unassigned to any applications results in an error when applicationId=0 is included in the query string
- BM-2182 - FIX: Editing legacy actions only scopes to correct application if the plan existed pre-v5.0 and does not take into account newly added legacy plans
- BM-2171 - FIX: Infrastructure export error with invalid agent or legacy server group
- BM-2170 - FIX: Infrastructure sync variable export can improperly nest JSON objects if a variable is marked sensitive
- BM-2177 - FIX: Legacy Set Variable action does not match v5.3 style package and release variables
- BM-2180 - FIX: Server roles variable editor does not refresh properly after deleting a variable, requiring the entire page to be refreshed
- BM-2181 - FIX: Variables page mistakenly displays variable migration button and legacy declarations when there are exactly 0 variables in the system
- BM-2174 - Improve help text when creating a Private Key credential from the Edit Server page
- BM-2169 - Indicate variable type ($,@,%) next to name in Variables Table
- BM-2179 - Show plan name and pipeline information on the Execution Details page
- BM-2161 - FIX: [PlanEditor] PsCall operation displays an error message when the script is an application-specific asset using an invalid qualified name character
- BM-2159 - FIX: [PlanEditor] PSCall with more than 15 parameters does not display a scrollbar and gets blocked behind the fixed button container at the bottom of the modal (requires Windows extension v5.3.3 or l
- BM-2160 - FIX: Creating a variable whose trimmed value is an empty string results in an error
- BM-2158 - FIX: Global Variables May Not Resolve
- BM-2162 - FIX: Pipeline details for stages with importers fail on plan validation
- BM-2163 - If any exist, display v5.3 style variables in release overview box on Application Overview page
- BM-2165 - Plan compilation, pipeline/stage, and other pre-execution failures should be logged to the execution log directly instead of linked
- BM-2164 - Release deployables page should be widened to support longer deployable names
- BM-2152 - Add CreateReleaseNoteOperation
- BM-2154 - Display latest execution date in the package deployment status timeline instead of initial promoted date
- BM-2147 - Display pipeline name on Release Templates overview page
- BM-2155 - FIX: Context iteration statement for deployables may skip a deployable if it is not included directly in the release even if it is referenced by a dependant deployable
- BM-2150 - FIX: Converted operation from Execute Command Line legacy action can fail if "import BuildMaster variables into environment" is set to true
- BM-2156 - FIX: Deployable variable functions may assume deployable name follows a stricter format than is actually allowed (i.e. an execution engine qualified name)
- BM-2145 - FIX: GMT timezone display bug for retention policies
- BM-2142 - FIX: Legacy executions combined with v5.3 style variables uses incorrect ordering to resolve value
- BM-2157 - FIX: Release number should default to "latest" and should not be required in the Deploy Release Package operation
- BM-2146 - FIX: Release templates that use global pipelines may persist incorrectly if local pipeline name matches
- BM-2141 - FIX: Remote ensure operations display incorrect descriptions in Plan Editor
- BM-2149 - FIX: SFTP copy file method should only pass -n when overwrite is not specified
- BM-2144 - FIX: Unique Key Constraint error should be captured more cleanly when promoting a package that was already promoted, either automatically or by another user
- BM-2148 - Hide Create button on Create Release page when there are no pipelines accessible by an application in addition to the error already displayed
- BM-2151 - INSTALLER: Always upgrade the 5 built-in extensions
- BM-2140 - Pipeline pages should indicate whether a specified plan name exists and give an error if no plan is found
- BM-2143 - When converting legacy plans on the application plans page, default to selected application to the current application regardless of legacy plan's application membership
- BM-2132 - Display a warning in the notification bar if the InedoCore extension is not loaded
- BM-2137 - FIX: 404 errors for nonexistent side-by-side CSS and JS files
- BM-2135 - FIX: Dragging a modal window in Chrome can hide the contents of the window unless the window is resized triggering an inner content resize first
- BM-2134 - FIX: Listed scope on Task page displays "system" for privileges that are scoped to a specific application group
- BM-2138 - FIX: Operations with custom ArgumentEditor may crash the PlanEditor UI
- BM-2131 - FIX: Partially loaded extensions whose assembly fails to load can cause the extensions overview page to crash
- BM-2136 - FIX: ScmBrowser Should Proxy ScmProviders to Agents When Needed
- BM-2130 - PlanEditor: Add "Disabled" Option for General Block
- BM-2133 - Release package triggers should include global pipelines as possible filters
- BM-2121 - Add "Legacy" Note to Configuration Profiles
- BM-2110 - Approval status on Build Overview should list all users who have marked approval, regardless of count required
- BM-2128 - Auto-expand execution logs all the way to the root if any descendants contain warnings or errors
- BM-2120 - Change Output Encoding on JSON API To Not Emit BOM
- BM-2113 - FIX: API reference overview documentation page errors out if there are duplicate, shimmed methods
- BM-2114 - FIX: Approval required event listeners defined at the system level only fire for certain applications even if no filter is applied
- BM-2129 - FIX: ArtifactsInPackage variable function can return the incorrect name if a source application's name differs from the artifact name
- BM-2125 - FIX: ExecuteScriptsOperation May Not Proxy to Remote Server
- BM-2112 - FIX: Global plans and global script assets should not be copied locally to the new application when cloning
- BM-2109 - FIX: Legacy plan editor should not require global Plans_Manage privilege to edit at the application level only
- BM-2123 - FIX: PlanEditor Boolean Values default to "" after editing which may cause value coercion problems at runtime
- BM-2122 - FIX: Re-Executing First Stage without Environment May Cause Error
- BM-2115 - FIX: Release deployables list on Create Package page does not populate if opened from the Packages Overview page because it does not apply the selected release number
- BM-2116 - FIX: Some operations with output arguments do not assign all values to outputs
- BM-2127 - FIX: Time-based promotion requirement cannot parse an "empty" day correctly
- BM-2111 - FIX: When editing an existing trigger, saving a Release Package Trigger does not automatically close the modal window
- BM-2124 - Lower default time for automated gate approval check
- BM-2126 - Relax Rules on ExecutionChangeScriptsOperation for Different Deployables
- BM-2080 - Stack Notifications on Top instead of Hiding.
BuildMaster 5.2 - Supported
- BM-2092 - Add Generate Release Notes operation
- BM-2091 - Creating a new release should attempt to automatically determine its sequence
- BM-2100 - FIX: Cannot create release package triggers from the UI
- BM-2099 - FIX: Event Listeners overview crashes if there is an invalid XML configuration persisted
- BM-2101 - FIX: Get Latest operation should ensure target directory exists before invoking provider
- BM-2102 - FIX: Issues overview page over-aggressively HTML encodes issue descriptions
- BM-2085 - FIX: Long name overflow in pipeline status UI
- BM-2104 - FIX: Possible file corruption in legacy Deploy Artifact action when deploy as zip file via SSH for large artifacts
- BM-2103 - FIX: Username/Password credentials are sometimes improperly excluded from credential type lists
- BM-2105 - When transferring files from Windows to Linux, default to file mode 644 instead of 755
- BM-2084 - Add "Overwrite" Option to CreateArtifact Operation
- BM-2073 - Clarify that UseUniqueExecutionTempDirectory is only for legacy plan executions
- BM-2072 - FIX: Add deployable to all active releases checkbox does not add release deployable to active releases
- BM-2098 - FIX: Add Environment page uses invalid API method internally causing SQL exception
- BM-2071 - FIX: EventListeners on pipelines may not run after execution
- BM-2094 - FIX: Legacy Execute Shell Script action fails with proxying error
- BM-2089 - FIX: Legacy Promote Build action may not promote all packages
- BM-2082 - FIX: Legacy server group should not be a link on the Environment Details page
- BM-2095 - FIX: Legacy transfer files action does not recurse when given a directory with a trailing \
- BM-2074 - FIX: libssh2 native binary directory is not deployed correctly by installer for web application
- BM-2097 - FIX: Plans_Manage privilege should be required to open plan editor
- BM-2087 - FIX: Redeploying always uses plan name of previous execution instead of plan configured in pipeline
- BM-2093 - FIX: Remove spurious "resource ace/worker-xml.js and/or ace/worker-json.js does not exist in InedoLibWeb" errors from error log
- BM-2067 - FIX: Script assets should cause a validation error if spaces are added to the script name
- BM-2090 - FIX: SSH agent temp path is not exposed and defaults to /tmp/buildmaster unless it was converted from a legacy agent
- BM-2078 - Link to "Legacy Plans in BuildMaster 5.0" knowledge base article on the Convert to OtterScript page
- BM-2079 - Only display "Legacy plan variable support" when there are legacy plans
- BM-2064 - Add Shims for Deprecated Native API Methods
- BM-2062 - Change Default Sorting on All Releases Page by Latest Promotion Date
- BM-2061 - FIX: Bash script staging directory is not always automatically created on SSH agents
- BM-2063 - FIX: Execute Change Script Operation May Zero-out GUIDS When PRoxying
- BM-2060 - Add CreateReleaseVariable Operation
- BM-2029 - API: Remove [AlwaysShowDeployables_Indicator] from Applications
- BM-2053 - FIX: "Pipelines Names Must Be Unique Per Application" Error Occurs
- BM-2059 - FIX: Clone Application Legacy Plans With Empty String Names Throws Error
- BM-2058 - FIX: Error attempting to add a release name for an existing unnamed release
- BM-2055 - FIX: Iteration block should include deployables in dropdown
- BM-2054 - FIX: Proxy Settings Page May not Report Errors after Test
- BM-2052 - FIX: Remove BuildMaster logo from Generate Release Notes legacy action template to prevent the missing "red X" in email clients
- BM-2057 - FIX: Set Variable Value Does Not Accept ${ } style names
- BM-2056 - Increase Visibility of Additional Pipeline Options in Editor
BuildMaster 5.1 - Supported
- BM-2051 - Add button to refresh server statuses on the Server Overview page
- BM-2043 - Better error message for usage of an undefined variable
- BM-2050 - FIX: Consumers of RemoteJobs that call ILogger.Log() only get written to the execution log when called from Execute() method directly
- BM-2042 - FIX: Create/Extract zip regression for SSH agents
- BM-2048 - FIX: Deleting a Legacy Plan Redirects to Global Plans instead of Application Plans
- BM-2049 - FIX: Legacy Deploy Artifact action may deploy more files than necessary in some incremental deployments
- BM-2045 - FIX: Legacy plan import/export options do not appear when the Import/Export button is clicked
- BM-2047 - FIX: Manual Action and Operation emails link to an invalid execution URL
- BM-2046 - FIX: OtterScript != predicate operator has incorrect precedence
- BM-2035 - Add optional "deployable" argument to $ReleaseNumber function
- BM-2039 - FIX: Email Attachment field in Visual Editor
- BM-2037 - FIX: Perform-ManualOperation exception with blank task description
- BM-2040 - FIX: Possible NullReferenceException in legacy manual action
- BM-2038 - FIX: Some large Windows->Linux file transfers can be corrupted
- BM-2041 - FIX: Upgrades from 4.9 can break legacy agent auto-updates
- BM-2036 - Improve legacy action error in OtterScript visual editor
- BM-2034 - Trigger server scan when an agent configuration is saved
- BM-2030 - Always Show Deployables when there are 1+ Deployables
- BM-2033 - FIX: Installer Crashes on Upgrades with Invalid Encryption Key
- BM-2032 - FIX: Purge ReleasePackage / Release May not Purge All Executions
- BM-2031 - FIX: URL Trigger Fails when Null Agent String is Passed
- BM-2025 - Add Rename Warnings for Servers, Environments
- BM-2026 - FIX: Add Validation for Legacy Agent Names
- BM-2018 - FIX: Auto-deploy to next pipeline stage
- BM-2023 - FIX: Clear directory command does not always delete all files when using SSH agents
- BM-2020 - FIX: Clone Applicationing Doesn't Copy All Application Variables
- BM-2024 - FIX: Delete-Files operation excludes more files than it should on SSH agents
- BM-2021 - FIX: Execution temp directories not getting cleaned up for OtterScript plans unless UseUniqueExecutionTempDirectory is set to true
- BM-2028 - FIX: JSON API displays incorrect remarks/descriptions, fix for SOAP API RyuJit regressions
- BM-2022 - FIX: Legacy agent name is incorrect in UI
- BM-2019 - FIX: PasswordTextBox Persistence
- BM-2027 - Use Specified tmp folder for script execution on SSH servers
- BM-1999 - FIX: Clone Application may timeout
- BM-2013 - FIX: Cloning an application does not assign new v0.0.0 release to cloned pipeline
- BM-2012 - FIX: Creating multiple Deployment template variables with the same name can fail with different stage targets
- BM-2016 - FIX: Database connection update will impact other connections
- BM-2017 - FIX: Saving Time-based Promotion Requirements for Days of Week
- BM-2015 - Minor Release - see http://inedo.com/buildmaster/5.1 for more details on new features
- BM-2014 - See the BuildMaster Beta v5.1 Notes in the Knowledge Base
BuildMaster 5.0 - Supported
- BM-2011 - FIX: BuildImporter and NULL Environment Pipeline Bugs
- BM-2010 - FIX: Variable entry for Create New Build legacy action does not persist new values correctly
- BM-2006 - FIX: Add Cascade Deletes to BuildScheduleVariableDefinitions
- BM-2008 - FIX: Cannot edit multi-repository providers that were created in between v4.7 and v5.0
- BM-2004 - FIX: Configuration File Deployment may not replace Runtime variables (only configuration)
- BM-2000 - FIX: Error Cloning Application with Global Pipeline
- BM-2009 - FIX: Invalid EventListeners on a Pipeline Cause Deserialization Error
- BM-2002 - FIX: Jenkins Plug-in May See 404s when using the BuildMaster API
- BM-2005 - FIX: Null AllowedIP Range may Crash Scheduled Triggers View
- BM-2001 - FIX: Permissions error using build step without environment association
- BM-2003 - FIX: Permissions resolution for /plans and /template-plans
- BM-2007 - FIX: Templates without descriptions cause errors in visual editor
- BM-1996 - Add description to templates
- BM-1991 - Allow Configuration Templates to be Deployed with Warning
- BM-1993 - FIX: Build importer with null environment causes error on import
- BM-1994 - FIX: Cancel button is in the wrong place in SCM browser modal
- BM-1992 - FIX: Copy-Files recursion errors
- BM-1998 - FIX: Do not allow local server to be renamed
- BM-1990 - FIX: Error Creating Configuration File Instance Without Environment
- BM-1988 - FIX: Error Setting Relative Monthly Trigger SChedule
- BM-1997 - FIX: Transfer-Files operation can create files with \ characters on linux
- BM-1989 - FIX: Wrong URL to edit server groups from environments overview page
- BM-1995 - Improve behavior for default pipeline of new release
- BM-1980 - Export Configuration File operation should not be browsable in the Visual Editor, in favor of Deploy Configuration File
- BM-1984 - FIX: Attempting to edit/delete an SCM Release Package trigger from the UI fails if the SCM connection is invalid or missing
- BM-1986 - FIX: Auto-generated variable function documentation always shows string and list prefixes for all functions regardless of actual type
- BM-1981 - FIX: Call Template Statement in Visual Editor results in invalid OtterScript syntax
- BM-1982 - FIX: Error deleting an obsolete extension from the UI when there was a load error
- BM-1983 - FIX: Purging a release package fails from the UI
- BM-1987 - Include $Eval Variable Function
- BM-1978 - Add @DeployablesInRelease([AppId], [RelNo], [IncludeImported]) variable function
- BM-1974 - FIX: Better handling for invalid call template statements in plan editor
- BM-1975 - FIX: Cannot change application pipeline to global pipeline for some releases
- BM-1976 - FIX: Create release page may ignore selected release deployables
- BM-1979 - FIX: Do not allow template plans with invalid names to be created
- BM-1977 - Release overview block on Application Overview page should link to issues filtered by that release instead of Top 25 issues for any release
- BM-1973 - BuildMaster 5.0 Major Version - see the upgrade notes at http://inedo.com/support/kb/1117/upgrade-notes-for-buildmaster-50
- BM-1970 - View the BuildMaster 5.0 Beta Notes at: http://inedo.com/support/kb/1116/buildmaster-50-beta-notes
- BM-1969 - View the BuildMaster 5.0 Beta Notes at: http://inedo.com/support/kb/1116/buildmaster-50-beta-notes
- BM-1968 - View the BuildMaster 5.0 Beta Notes at: http://inedo.com/support/kb/1116/buildmaster-50-beta-notes
- BM-1967 - View the BuildMaster 5.0 Beta Notes at: http://inedo.com/support/kb/1116/buildmaster-50-beta-notes
BuildMaster 4.9 - Beta
- BM-2231 - FIX: Delete on Long File Path May Cause ArgumentNullExceptions
- BM-2223 - FIX: Add Failure Logging to InitializeRemoteConfiguration
- BM-2086 - Add "Do Not Use" Note on "Convert to OtterScript Preview"
- BM-2077 - Add Warning for Deprecated & Custom Extensions
- BM-2075 - Add Warning for PurgeArtifactsEventListener Usage
- BM-2076 - Add Warning that Triggers/Notifiers will be Purged
- BM-2081 - FIX: Clone Application with Config Files with Duplicate Names in Same Deployable Crash
- BM-2088 - FIX: Permissions may restrict editing application-level workflows
- BM-1961 - Add "Closed issues only" option to Generate Release Notes Action
- BM-1962 - FIX: $ExpandVariables function does not work in legacy plans
- BM-1959 - FIX: Add redirect for open tasks
- BM-1964 - FIX: Change script count filter does not respect "all" option
- BM-1963 - FIX: Executing variable functions with arguments can cause an executer exception in converted OtterScript plans
- BM-1958 - FIX: The error message displayed when adding a change script with a duplicate name should be more clear
- BM-1957 - FIX: Viewing the details of a synchronized JIRA issue can result in an error page if the description is missing
- BM-1960 - Hide servers from Deploy Configuration File page if the ConfigurationFiles_DeployConfigurationFile task is restricted for an environment that contains the specific server
- BM-1965 - Update Generate Release Notes Action template to use the v4.X template
- BM-1954 - "Add Change Script" button should also appear at the top of the page
- BM-1955 - Configuration File Overview page should indicate when there are no deployables configured for an application.
- BM-1953 - Default encoding for Export Database Change Scripts should be UTF8
- BM-1950 - FIX: Null reference exception caused by invalid filters in legacy issue tracking providers
- BM-1949 - FIX: Providers that only expose the newest interfaces for issue trackers that can create and deploy releases may not execute consistently
- BM-1951 - FIX: Purge operations fail when there are zombie scheduled promotion records that are not cleaned up properly
- BM-1952 - FIX: Type conversion error when attempting to save Export Database Change Scripts action
- BM-1947 - Add setting for verbose retention policy logs
- BM-1946 - Add support for displaying and filtering by synchronized issue types
- BM-1945 - Add an option to exclude the failed action log in the Execution Completed Email event listener
- BM-1943 - Allow closed and opened build numbers to be configured manually for synchronized issues
- BM-1944 - Differentiate between issues opened in a build vs. issues that are still open from a previous build
- BM-1941 - FIX: Build importers do not function correctly for some providers
- BM-1942 - Set the "Opened on Build Number" and "Closed on Build Number" fields if a build is created whose release references a new or closed issue tracker issue with the corresponding field being null
- BM-1938 - Allow Database Change Scripts to be filtered by the latest execution status
- BM-1937 - Allow sorting of Database Change Scripts to be persisted in the query string for bookmarking
- BM-1940 - FIX: $ApplicationDirectory variable should include trailing directory separator for OtterScript plans
- BM-1939 - FIX: Database Change Scripts sorting ceases to function after the table contents are reloaded dynamically
- BM-1936 - FIX: DatePicker calendar does not appear on Create Release page when the text box is selected
- BM-1935 - Add sort capability to Change Scripts Overview table
- BM-1931 - Always show the table for imported deployables
- BM-1893 - Database Change Script Overview should have a status image denoting the last execution status
- BM-1918 - FIX: ApprovalRequiredEventListener should not require Manage All Privileges
- BM-1933 - FIX: Broken link to create SCM-triggered automatic build on Automatic Builds Overview page
- BM-1929 - FIX: Deployable context set statement should skip the block when deployable is not included instead of raising an error
- BM-1916 - FIX: Error deleting servers with variables associated in some cases
- BM-1934 - FIX: Retention policies that complete and log more than 8KB of data are truncated in the purge history
- BM-1930 - FIX: Test Connection reports "object reference not set" error when attempting to test a connection with any provider
- BM-1932 - Log non-connection related exceptions in error log when testing a provider connection
- BM-1926 - Add version to config file deployment history
- BM-1928 - FIX: $ApplicationDirectory is no longer adding a trailing \ character to its returned path
- BM-1927 - FIX: Regression in weekly build schedule
- BM-1924 - Add option for execution-unique temp directories that are automatically cleaned up
- BM-1923 - Add Otter-style execution engine
- BM-1922 - FIX: Deploy artifact action can incorrectly set file timestamps
- BM-1921 - FIX: Some recurring scheduled builds can be skipped
- BM-1920 - Increase visibility of deployed build number on Release Overview page
- BM-1925 - Reduced page load time for release overview page
- BM-1895 - Remove "executions on this server" from server page
BuildMaster 4.8 - Limited Support
- BM-1913 - Add setting to disable agent command queuing
- BM-1911 - FIX: Cannot view logs for retention policies that have null log entries
- BM-1912 - FIX: Inactive applications display on All Apps Page
- BM-1914 - FIX: Race condition causing error on action finalization in parallel action groups with default source and target directories
- BM-1915 - Stage temporary build artifact files outside of application-specific temp directory
- BM-1900 - Add "Do not Execute option" on Promote Build Page
- BM-1909 - Allow background server check trigger on Server Overview page to be disabled
- BM-1908 - Allow option to enforce server environment associations at deployment time
- BM-1903 - Clarify "scheduled to occur in the future" message when the execution has not started at its scheduled time
- BM-1899 - Display the issue tracker issue ID on the Issues Overview page instead of the incremental ID
- BM-1901 - FIX: An imported deployable's artifact cannot be deployed unless there was at least 1 promotion for the build containing that artifact when "UseFurthestBuildForImportedDeployable" option is set to tru
- BM-1894 - FIX: Assign unique HTML ID to login page form fields so that browser password managers can remember the password
- BM-1873 - FIX: Changing release on Import Build does not update build importer defaults
- BM-1896 - FIX: Deployable variables should only be allowed to be added when editing the deployable
- BM-1898 - FIX: File System Build Importer does not respect the file mask set in the template
- BM-1888 - FIX: Issue details should show who created the issue
- BM-1897 - FIX: Manual configuration file deployment page should not display restricted instance environments
- BM-1905 - FIX: Release Closed event listener should subscribe to the Release Deployed event instead of the Build Promotion Completed event
- BM-1910 - FIX: Transfer Files action should always copy modified timestamp value
- BM-1887 - Force release number selection when creating a new build when there are multiple active releases and the context for creation is not already in a release
- BM-1892 - Increase database change script max name length to 250 characters
- BM-1906 - Performance improvements to some pages that call Release_GetReleases in the SQL API
- BM-1907 - Wrap long application names without spaces or dashes on Application Overview page so they do not appear beneath the environment boxes
- BM-1889 - FIX: Missing method exception displayed in certain recipe summary items instead of actual summary
- BM-1875 - Add Global Workflow, Environment Filter to All Applications page filter
- BM-1884 - FIX: Edit workflow pages privilege restrictions are too strict if users are assigned Manage Workflow privileges to an application scope only
- BM-1885 - FIX: Unable to select app to delete/purge in some situations
- BM-1886 - Increase visibility of Issue Tracking Post-Deployment Events
- BM-1880 - Add "View Full Log" button to Execution Details page
- BM-1879 - FIX: Build importer on triggered build may request invalid build number in some cases
- BM-1882 - FIX: Change Control pages display server errors in place of certain content sections
- BM-1877 - FIX: Type conversion error in logs occurs when saving a post-build step on the workflows page
- BM-1874 - FIX: Unwrap aggregate exceptions on get SCM state
- BM-1883 - FIX: ViewDebugLogs privilege not applied to build step correctly in certain cases, and it should also be more clear that logs are hidden when privilege is restricted
- BM-1878 - Improve error message when unable to increment build number
- BM-1876 - Limit number of active releases on BuildMaster Overview page to 30 for performance reasons
- BM-1866 - Add retries to action finalization
- BM-1865 - FIX: Incorrect formatting for some simple HTML elements in field descriptions
- BM-1870 - FIX: Manually configuring a new server does not populate the default port number for the self-hosted agent
- BM-1872 - FIX: Plans_ViewGlobalPlans permission is not applied to the editor correctly when Plans_ManageGlobalPlans privilege is missing/restricted
- BM-1867 - FIX: Source control providers link is incorrect
- BM-1868 - If directory information in deployment plans is truncated at 50 characters, show the full path in a mouseover tooltip
- BM-1871 - Use a separate privilege to determine whether a user can view an action's details vs. modify them
- BM-1848 - Add "Crash on DB failure" option to the service
- BM-1862 - Add "Purge Orphaned Artifacts" option to purge artifacts retention policy
- BM-1851 - Add ambient variables to script repository
- BM-1861 - Add Copy Files action to copy files on one server
- BM-1864 - Allow application group groupings
- BM-1860 - FIX: Long path support does not work with UNC network shares
- BM-1863 - FIX: Possible HTTP 500 error when deleting the last action in an action group
- BM-1776 - FIX: Sticky "cannot communicate with database" error message
- BM-1806 - FIX: Update status on SSH agents after key changes
BuildMaster 4.7 - Limited Support
- BM-1852 - BuildMaster installation fails if installing with custom SQL Server with a database collation set to some value that is case-sensitive
- BM-1847 - Clarify behavior of "Convert Application Workflow"
- BM-1849 - FIX: Allow privilege modification for non-current directory provider
- BM-1854 - FIX: Deployables assigned in Build Importer templates on the build step are not cascaded properly to the actual Build Importer itself
- BM-1857 - FIX: Import Action Group via copy link does not include build step deployment plans
- BM-1858 - FIX: Import Action Group via copy should display the name of the workflow associated with each plan instead of duplicating the environment name
- BM-1850 - FIX: In Firefox, the proxy configuration test results in a "Error: [object XMLDocument]" message if the test succeeds
- BM-1855 - FIX: Incorrect description of unzip file action on deployment plan overview
- BM-1853 - FIX: SDK compatibility broken for Applications_EditApplication & Applications_GetApplications
- BM-1856 - FIX: Setting a future execution without specifying a time will never execute the promotion
- BM-1842 - Add "Select Default" and "Select None" options to the release deployables selection
- BM-1837 - Allow for "soft-delete" of applications to hide them from navigation menus but preserve historical data
- BM-1839 - Allows users to add favorite applications, which appear first in the navigation menu
- BM-1836 - FIX: Canceling a release should not change the rejection date of rejected builds
- BM-1834 - FIX: Default HTTP-based actions incorrectly interpret old "fail if response is not HTTP 200" setting when converting to response code error range
- BM-1844 - FIX: Deleting a deployment plan used by an active workflow, then promoting to that environment can invoke undefined behavior, instead of simply running a "do-nothing" execution
- BM-1835 - FIX: Duplicating an application with multiple releases fails with FOREIGN KEY error if there is also an application variable
- BM-1838 - FIX: In certain circumstances, cloning a workflow will assign the copied deployment plans to the incorrect new workflow step
- BM-1843 - FIX: Issue summary list on build page checks for Issues_CloseIssue instead of Issues_ViewIssue
- BM-1840 - FIX: Saving a release note and selecting an associated environment without a build should show a friendly error message
- BM-1841 - Include the user who created the original build and the date/time it was originally created in the Deployment Execution Completed event listener
- BM-1820 - Add $ConfigurationFileVersion and $ConfigurationFileText variables
- BM-1832 - Add $ExecutionStatus variable
- BM-1810 - Add a tag-textbox variable that resolves to a CSV list of selected values
- BM-1824 - Additionally copy application and deployable variables when duplicating an application
- BM-1831 - Change HTTP POST and GET actions to allow the user to pick the HTTP verb for RESTful operations, and optionally save the response body in a variable
- BM-1833 - FIX: Create Issue button on build page should default the "Opened in Build" option to the relevant build number
- BM-1829 - FIX: Privileges that are denied to an application group and environment are incorrectly applied to other applications that are not in the group
- BM-1828 - FIX: Purge Build fails with an "Invalid object name" error message
- BM-1830 - FIX: Recipe to change agent type fails with update error
- BM-1801 - Add server-specific option to not log agent updater errors
- BM-1826 - FIX: "Sequence contains no elements" no error on delete action group page with invalid ID
- BM-1822 - FIX: Build Importers do not respect the workflow step's Build Importer Template's extension configuration when more than one profile exists for an extension
- BM-1823 - FIX: Build steps assigned to global deployments plans displays a "given key was not present in the dictionary" error
- BM-1825 - FIX: Ensure that any change to privileges, roles, users, or groups results in the cache being cleared, and add a button to manually clear it
- BM-1821 - FIX: Logic that determines whether to demand privileges for "ManagePlans" and "ManageGlobalPlans" is incorrect when editing an action group
- BM-1819 - FIX: Set timeout to 15 minutes for RetentionPolicies_GetBuildsWithLogsToPurge() in Purge Logs retention policy
- BM-1797 - A deployment plan that is shared should be indicated with a shared icon (similar to the globe icon) in the deployment plan tabs
- BM-1813 - Clarify shared/copied deployment plans between workflows and distinguish build from deployment plans
- BM-1809 - FIX: Ensure command line arguments are not logged during service installation
- BM-1708 - FIX: Environment names are hidden when they overflow on the builds-per-environment timeline
- BM-1791 - FIX: Selecting a deployable when uploading a change script should be marked as a required field
- BM-1816 - Improve post-release behaviors on Workflow page and only display them if they are active
- BM-1817 - New application picker - improve performance, allow searching for applications/groups
- BM-1763 - Option to not hide deployables if only a single
- BM-1800 - Add option to set Windows service name for silent agent install
- BM-1796 - Better handling for null variable values in Execute Command Line Action
- BM-1788 - Better handling for orphaned service on BuildMaster installs
- BM-1812 - Create Artifact Action on the SSH Agent should maintain symbolic links in a zip archive instead of reifying them
- BM-1709 - Do not allow disassociating a workflow that is still in use by an active release
- BM-1789 - FIX: Broken workflow link on the Release History page
- BM-1805 - FIX: BuildMaster SDK compatibility issue for extensions that rely on ConfigurationFileDeployer
- BM-1799 - FIX: Configuration file "Set Version" button on the Release Overview page validates privileges at the system level instead of at the application level
- BM-1802 - FIX: Create Build Artifact action does not work for paths longer than 248 characters
- BM-1743 - FIX: Duplicating an application which has a build step that was cloned from the same application can issue a foreign key constraint error
- BM-1794 - FIX: Duplicating an application with event listeners in each workflow steps can fail with a constraint error
- BM-1793 - FIX: Event listeners assigned to a workflow/build step that are inactive are difficult to see on the overview page
- BM-1758 - FIX: Many variables makes it hard to determine which scope the variable is in because of vertical-middle alignment
- BM-1815 - FIX: Possible race condition with installer may cause CLR20r3 error on launch
- BM-1808 - FIX: Refresh servers page after saving a server group
- BM-1814 - FIX: Transfer Files action does not work for paths longer than 248 characters when source and target are the same server
- BM-1727 - Improve documentation for $CurrentDirectory
- BM-1772 - Lighten text of versions with unmodified instances in compare config file version dropdown
BuildMaster 4.6 - Limited Support
- BM-1782 - Add JSEncode variable function for Javascript string encoding
- BM-1786 - Agent updater should only consider .bmx files as extensions
- BM-1783 - FIX: Config file pages are inaccessible to users that have had one or more instance restricted by privileges
- BM-1777 - FIX: Create Release action editor does not save specified variable values
- BM-1785 - FIX: Deleting a role can result in an HTTP 500 error
- BM-1784 - FIX: Service status page sometimes does not load if the service is not running
- BM-1779 - FIX: Upload Artifact administrative edit does not allow deployable to be specified
- BM-1778 - FIX: Web<->service connection can get in a broken state requiring service restart
- BM-1730 - Improve HTTP Post action
- BM-1787 - TR__ActionGroupActions__ValidateSequence trigger should not fire on updates
- BM-1762 - Ace Code Editor plugins should be upgraded to support syntax highlighting/coloring for SQL, XML, Bash, VBScript and PowerShell
- BM-1765 - Allow Configuration Files to be manually deployed to server groups instead of just servers
- BM-1767 - FIX: Change Controls approval does not filter environments correctly
- BM-1775 - FIX: Day/Time pre-deployment approval checklist option should not default to "none" for the days of the week field
- BM-1770 - FIX: Display comments in Build Approvals gadget for historical builds in addition to requirement description and time approved
- BM-1774 - FIX: Event listeners are sent multiple times when assigned directly to a Post-Build step
- BM-1729 - FIX: Exporting deployment plans should default to the application & environment's name when exported from within the context of an application, and should use the deployment plan name if it's global
- BM-1771 - FIX: Not entering a role or task in the assign privileges page will result in a IndexOutOfRangeException instead of displaying the field as required
- BM-1769 - FIX: Permissions are incorrectly applied when there are restrictions to specific tasks only
- BM-1768 - FIX: Releases_CreateReleaseNumber fails with high but still valid release numbers
- BM-1728 - Add alternative suggestion when executing a .lnk or .bat file directly fails with "The specified executable is not a valid application for this OS platform" message
- BM-1747 - Add support for CTRL+F search in config file editor
- BM-1760 - Allow release name to be specified in the "Create New Release" action
- BM-1733 - Allow Server List Variable to be filtered by environments
- BM-1761 - API: Add Releases_GetNextReleaseNumber method that returns the expected next logical release number based on the release numbering scheme
- BM-1745 - Clarify "Service is OK" message when there is a "cannot connect to database error" directly above it
- BM-1724 - Display list of deployables that are included with the release in the Execution Completed event listener
- BM-1755 - Do not remove the green plus icon to add variables at specific scopes so that more than one can be created without having to visit the Variables pag
- BM-1736 - FIX: Attempting to clone an application with configuration files may fail with "TransformType_Code"-related error message
- BM-1752 - FIX: Cannot purge release when there are configuration file deployments associated directly with that release
- BM-1744 - FIX: Clicking in code editors is kind of funky in IE
- BM-1732 - FIX: Create Release Number should warn about 11+ chararacter release numbers
- BM-1756 - FIX: Create Release should be hidden if "Allow multiple active releases" is unchecked for the application
- BM-1749 - FIX: Deployable selection when downloading a change script deployment tool from the web application does not generate a change script deployment tool based on that selection
- BM-1741 - FIX: Duplicating an application and selecting "Link only action groups" does not link correctly with the source application
- BM-1742 - FIX: Importing deployment plan from XML ignores actions in action groups that are Shared with other action groups in the system
- BM-1746 - FIX: Post-Build Auto-Deploy Step Deletes upon Workflow Property Save
- BM-1753 - FIX: Re-execute promotion link on Execution Details page opens a modal that is not sized correctly, and it should also be combined with the re-execute page
- BM-1737 - FIX: Selecting "Create new..." in the release dropdown on the Create Build page should stay within the modal page instead of changing the target=parent's window
- BM-1750 - FIX: Server name variables should have spaces trimmed when saved
- BM-1748 - FIX: Set Variable Value action should be an agent-based action
- BM-1738 - FIX: The Create Release page should show an error when attempting to create a release with the same number as one that already exists instead of silently closing the modal
- BM-1757 - FIX: Trim server names of spaces on save to prevent possible issues with variable servers in the future
- BM-1734 - FIX: Width of Add Script dialog does not scale to a readable size correctly
- BM-1731 - For custom Create New Application wizards on the New Application page, show the custom extension icon if there is one in place of the default grey question mark
- BM-1711 - Improve rules for active license key selection
- BM-1751 - Infobox wording that is shown when there is only a single workflow step does not take into account the build step, and may be confusing
- BM-1714 - License can display as invalid if an approval-only user was created and licensed with a previous key that allowed approval-only users, but the newer key does not
- BM-1725 - Link to the Script Repository from the Execute Shell Script and Execute PowerShell Script actions for better visibility
- BM-1710 - Make anonymous deployment plans hidden by default on manage deployment plans page
- BM-1726 - On Create Release page, default the value of the next release to the same value as what "auto-increment" on the workflow would set it to
- BM-1707 - Add link to show inactive configuration file instances, and make it easier to restore them
- BM-1723 - Improve configuration file selection during automated deployment such that it attempts to match by deployable, name, then path; but only if configuration file names match
- BM-1719 - Add Retention Policies
- BM-1720 - Administrative Edits
- BM-1717 - Display the configuration file alias instead of instance name on the Release Overview page
- BM-1718 - Expand variables in values of key/value pair config file templates
- BM-1722 - FIX: Configuration files should search other deployable's configuration files by name if one is not found by the same name for an action group's current deployable
- BM-1721 - FIX: Configuration files with multiple templates do not preview correctly when deploying them manually
- BM-1706 - FIX: Drag/drop action groups for deployment plans may not refresh UI correctly
- BM-1712 - FIX: Ignore deploy artifact or unzip file errors that are the result of an invalid zip file with a root entry of "/"
- BM-1715 - FIX: Search/replace in files action should allow empty text as replacement text in the action editor
BuildMaster 4.5 - Limited Support
- BM-1697 - Administrators can now require a user to change passwords on next login
- BM-1700 - Allow database change scripts to also be entered directly as text instead of requiring a file upload
- BM-1703 - FIX: Cannot recreate a previously deleted config file instance
- BM-1702 - FIX: Database change script filter does not reset after closing the edit window and instead loads all change scripts, which can slow page load time
- BM-1698 - FIX: Duplicating an application should also duplicate the "Allow Local Changes" flags for workflows and deployment plans
- BM-1701 - FIX: Event listeners with no editable fields or custom editors will be duplicated if added only once
- BM-1705 - FIX: Importing deployment plan loses the parallel flag for deployment plan action groups
- BM-1696 - FIX: Rejecting builds with multiple releases may cause other release's builds to be rejected if they are in the same environment and there are no other builds for that release
- BM-1699 - Improved action group copying logic
- BM-1704 - Redirect back to create build page if editing release deployables from the manage deployables link on the create build page
- BM-1692 - Add ability to restore an inactive application workflow
- BM-1694 - Add contingent promotion predicate
- BM-1693 - Allow build number scheme to be changed after application is created
- BM-1695 - FIX: Deploy all config files action fails if there are files without a matching instance name
- BM-1691 - FIX: Execution Completed event listener email should not include promotion data when not applicable
- BM-1690 - FIX: Expand all and collapse all links on deployment plan editors sometimes do not work correctly
- BM-1663 - Add setting to disallow changes to a global deployment plan from an application
- BM-1662 - Add workflow setting to disallow changes to a global workflow from an application
- BM-1689 - Clarify approval steps required in Approval Required email
- BM-1687 - FIX: Allow deletion of application groups that are assigned to event listener filters
- BM-1685 - FIX: Attempting to create a release of an application that doesn't have any workflows and/or deployables should issue a warning
- BM-1681 - FIX: Cannot delete an individual file with a very long path
- BM-1684 - FIX: controlId error that appears on the Schedule Promotion page
- BM-1688 - FIX: Create new build editor radio buttons do not act like normal radio buttons
- BM-1686 - Improve description for Deployment Execution Completed event listener to include the user and whether logs are attached
- BM-1680 - Improve usability of purge application page
- BM-1683 - Persist action group collapse state in a cookie for deployment plan editors
- BM-1667 - Add Export Configuration File action that does not record deployments and allows templates to be written out to a server
- BM-1665 - Add option to send as HTML in email action
- BM-1672 - Allow manual agent updates and restarts to be forced from the UI
- BM-1676 - Approval Required event listener options should be more clear with regard to who receives the emails
- BM-1674 - FIX: All Applications page can show links to inaccessible applications
- BM-1656 - FIX: Approvals for out-of-order promotions cannot be supplied using the promotion checklist
- BM-1678 - FIX: Constraint error when deleting deployable with configuration files associated with a release
- BM-1673 - FIX: Escaped quotes are not always properly parsed when posting data to the JSON API
- BM-1677 - FIX: Even though it is not clickable, the Create Release button should not appear if the user doesn't have privileges to create a release
- BM-1675 - FIX: Event listeners can be duplicated for workflows even if they are not shared
- BM-1679 - FIX: Installer database backup always used database named "BuildMaster"
- BM-1655 - FIX: Release timeline create build link does not link to import build page when necessary
- BM-1666 - Log when an action group is skipped due to a deployable not being included
- BM-1669 - Add an alert warning to restart the BuildMaster service if more than half of the servers are in an error state
- BM-1671 - API: JSON API content type should only be application/json when the result is successful, and text/plain when a 400 or 500 error is returned
- BM-1638 - Approvals received for historical builds should be displayed in the Approval Checklist section
- BM-1668 - FIX: Link to create release page on Application Health page broken when an Empty application is created
- BM-1660 - FIX: Possible execution deadlock with small deployment plans when there are contingent promotions (SQL Server 2014)
- BM-1658 - FIX: Update extension page just stays spinning on Downloading forever
- BM-1664 - Improve Execution Status Predicate by clarifying wording and also allowing action group execution based on build execution warnings instead of just success and failure
- BM-1670 - Installer should retry staging Service directory in case of expected file locks
- BM-1659 - Use 245 instead of 250 for MAX_PATH trigger check
- BM-1651 - AD browser in installer should sort results
- BM-1652 - Allow external builds to be imported through the recurring and URL-triggered automatic builds interface
- BM-1654 - Extension configurer defaults should be applied per-property
- BM-1653 - FIX: Default configuration profile should not be required
- BM-1625 - Allow non-alpha in build number entry
- BM-1649 - FIX: Failed handshakes for TCP agents can result in sticky Error status
- BM-1648 - FIX: PowerShell CheckBox script library parameters are always initially unchecked in action editor
- BM-1650 - FIX: Triggered build URLs may not authenticate correctly when using the Integrated Web Server
- BM-1645 - Allow release scheme to be changed after an application has been created
- BM-1629 - Allow variable values to be blank
- BM-1624 - Clarify "No permission to communicate with service" resolution
- BM-1630 - Default focus to first input field in modal dialogs
- BM-1621 - FIX: A large number of variables in the variable editor contained on a modal page can cause the Save and Cancel buttons to align improperly
- BM-1647 - FIX: Approval required event listener does not validate against the correct environment when used a post-deployment step
- BM-1642 - FIX: Auto-promote can erroneosly occur to first environment after a build step
- BM-1646 - FIX: Using a PathCombine function in the target of a Synchronize Files action can fail the execution
- BM-1643 - Improve usability of Schedule Execution page
- BM-1627 - Installer should grant sufficient privileges to web application account to monitor service status
- BM-1644 - Installer should make sure app pool is shut down before an upgrade if using IIS
- BM-1628 - New releases should be auto sorted based on release number scheme
BuildMaster 4.4 - Limited Support
- BM-1635 - Add option when creating a deployable to "add to all active releases"
- BM-1640 - FIX: Cannot reexecute build step execution
- BM-1637 - FIX: Change Agent Type recipe has incorrect redirect URL
- BM-1634 - FIX: Deployable is not copied when an action is copied using the "copy to" dialog box
- BM-1631 - FIX: Editing an event listener will pre-populate the application group field with group that has an ID equivalent to a selected application
- BM-1616 - FIX: Event listeners do not filter by environments under certain circumstances
- BM-1641 - FIX: File system build importer can timeout if drop location is not specified
- BM-1636 - FIX: Given key not present error for build approval received notifier
- BM-1632 - FIX: Importing deployment plan from XML with an extension configurer does not validate correctly
- BM-1639 - FIX: Occasional SQL deadlock during short executions
- BM-1633 - Improve description of IntegratedAuthenticationEnabled configuration setting
- BM-1620 - FIX: Action groups assigned to dynamic variable servers do not pre-populate on the edit page
- BM-1617 - FIX: Cannot delete servers when software reverts from an Enterprise to a Free license
- BM-1614 - FIX: Execute Client Command action editor
- BM-1618 - FIX: Force promotion button should not appear to the user if they do not have Force privileges
- BM-1615 - FIX: Page title and heading on execution in progress page displays the underlying release number instead of name coalesced with the number
- BM-1622 - FIX: Reexecute from last failed skipping actions in subsequent deployable iterations
- BM-1623 - FIX: Transfer files action validates invalid path characters in paths even when there are variable functions present
- BM-1619 - Increase maximum length of workflow names to 50 characters
- BM-1626 - Warn if no files renamed in Rename Files Action
- BM-1610 - $Date variable function should accept a valid .NET DateTime format string as an argument
- BM-1608 - API: Applications_GetApplication should not generate a database error if the supplied application ID does not exist
- BM-1607 - Deployment plan overview page should order by name instead of DB ordering
- BM-1603 - Display current BuildMaster version number in Live Help sidebar
- BM-1595 - FIX: Add workflow tab doesn't work in Firefox v31-32
- BM-1606 - FIX: Application group variables not resolved correctly in executions when there are multiple application groups
- BM-1596 - FIX: Cloning a workflow copies approvals in that application instead of into the new one
- BM-1613 - FIX: Deleting a deployment plan that is in use results in an FK error
- BM-1612 - FIX: Deleting a workflow that is assigned to a filter in an Automatic Build will fail
- BM-1594 - FIX: Deploy All Configuration Files action has incorrect validation when used in a global deployment plan
- BM-1599 - FIX: Deployment plan page button link on Application Health page after creating an Empty application points to the wrong page
- BM-1600 - FIX: Error displaying error message for invalid custom editors
- BM-1604 - FIX: Execution completed event listener "send on failure only" option is not honored correctly
- BM-1598 - FIX: Import deployment plan page results in "Nullable object must have value" error message
- BM-1611 - FIX: More than 1 application group variable entry should be allowed
- BM-1602 - FIX: Using "copy to" for an action group into another application will assign an incorrect deployable
- BM-1605 - Improve TCP agent connection error reporting by including the WIN32 socket error code
- BM-1609 - Performance optimization for promotion completion
- BM-1597 - Show a severe error alert bar message if the BuildMaster service cannot open or connect to the BuildMaster database
- BM-1591 - FIX: Button to deploy build for workflows without automatic release build in final environment is hidden when it should not be
- BM-1592 - FIX: Deploy artifact action may use wrong temp directory with agents hosted by underprivileged user accounts
- BM-1590 - FIX: Execution variables should be allowed to be assigned to Build Step
- BM-1593 - Increase visibility of builds marked as deployed on the build overview page when part of a workflow that doesn't automatically deploy builds
- BM-1589 - When deleting a global deployment plan, redirect back to Global Deployment Plan Overview page instead of the Admin page
- BM-1586 - Allow Deploy Configuration File action to specify a different name to be used on deployment
- BM-1571 - Create New Release action should allow variable application names in addition to the dropdown with specific applications
- BM-1579 - FIX: %Agent_Url% is not replaced in server status notification emails
- BM-1581 - FIX: Approval required event listener does not work for certain applications
- BM-1585 - FIX: Attempting to add a Deploy Configuration File action will produce a meaningless warning when editing an action group in a deployment plan shared with another environment in the same application
- BM-1580 - FIX: Automatic promotion requirements are not always evaluated when they should be
- BM-1574 - FIX: Deploy config file action should not list inactive config files
- BM-1576 - FIX: Deploying artifacts for the same deployable on the same server in parallel may fail
- BM-1587 - FIX: Display any server variable resolution failures on the Live Details page
- BM-1578 - FIX: Execution completed email event listener does not work if no user name is specified
- BM-1584 - FIX: Import Build menu option results in an error message when multiple workflows are assigned to active releases with different build import configurations
- BM-1575 - FIX: Releases_PurgeReleaseData API method does not work
- BM-1582 - FIX: Show Status of Execution on Build Timeline
- BM-1588 - FIX: View execution details link in the header bar should not appear if the user does not have privileges to view the execution in its environment
- BM-1567 - FIX: Workflow links on Global Deployment Plans page do not link to the correct page
- BM-1583 - Improve visibility of rejected build status on the Build Overview page
- BM-1572 - FIX: Action groups without a name cannot be expanded on the Execution Details page
- BM-1568 - FIX: Build importer errors do not always fail the execution
- BM-1548 - FIX: Change control environment ordering does not honor workflow ordering
- BM-1569 - FIX: Clicking on Builds button on navigation bar has odd behavior when there are no active builds
- BM-1502 - FIX: Extension configurers can't be deleted if they are used somewhere in a deployment plan
- BM-1565 - FIX: Re-execute from last failed action does not always import last execution's variable values
- BM-1564 - FIX: Re-execute from last failed action does not work if deployment plan uses no servers
- BM-1570 - FIX: Re-executing a promotion may result in a null variable name or value
- BM-1563 - FIX: Scheduled promotion executer is only triggered if an auto-promotion execution completes
- BM-1573 - FIX: Source control picker does not show the window used to select a source control path on the SCM-triggered build page
- BM-1566 - Inactive workflows should be a separate section on the global workflows page
- BM-1500 - Allow notifiers to be filtered by application group
- BM-1562 - Fixed beta issues
- BM-1158 - Add application/environment-specific triggers
- BM-1556 - Add optional Build pseudo-environment to workflows
- BM-1557 - Add support for build importers for CI tools
- BM-1559 - Allow promotion to automatically occur if all approvals/requirements are met
- BM-1558 - Allow promotions to be scheduled
- BM-1554 - Allow workflows to be reusable
- BM-1555 - Improved workflow editor
BuildMaster 4.3 - Limited Support
- BM-1551 - FIX: ArgumentOutOfRangeException possible from DirectoryHilite.ShortenPath
- BM-1552 - FIX: Executer does not fail execution if exception is caught during action deserialization
- BM-1549 - FIX: ManageConfigurationFiles privilege should not be required on the configuration file overview page
- BM-1550 - FIX: Renaming a deployable does not propagate to deployment plan action groups
- BM-1546 - FIX: Server variable replacements are not made when deploying configuration files
- BM-1543 - FIX: Duplicating an application should not require individual table ownership in the BuildMaster database
- BM-1545 - FIX: If sharing, only full deployment plans can be shared when duplicating an application
- BM-1544 - FIX: Importing deployment plans should include parallelism
- BM-1541 - FIX: When importing a deployment plan, invalid arguments are passed to the page that performs the import
- BM-1539 - FIX: Promotions with no deployment plan can cause execution to hang for some applications
- BM-1531 - FIX: Applications with shared action groups in the same deployment plan will not clone correctly
- BM-1529 - FIX: Autocomplete textboxes with placeholder text show autocomplete window on page load in IE 10+
- BM-1533 - FIX: Canceling an execution while it is in a pending state can prevent later executions for that application from running until the service is restarted
- BM-1537 - FIX: Checking if a manual action has completed yields a DB transaction error
- BM-1535 - FIX: Concatenate files action should note that the output file field is required
- BM-1536 - FIX: Empty string literal arguments to variable functions do not work
- BM-1528 - FIX: For some failed executions, clicking on "View Details" button brings the user back to the Execution in Progress page instead of the actual Execution Details page
- BM-1538 - FIX: Link to Upgrade Notes on the "Updates Available" page points to a broken link
- BM-1534 - Improve UI for promotions scheduled in the future
- BM-1530 - Improve UI for workflow predicate
- BM-1532 - NotifierExecuter should run immediately after important events
- BM-1519 - FIX: Cancel button on Add New Action Modal does not close window
- BM-1520 - FIX: Cannot copy to adjacent action or last action using CTRL-drag in the deployment plan editor
- BM-1526 - FIX: Cannot import action group in empty application unless 1 or more action groups exist
- BM-1525 - FIX: Cloning applications fails unless done via the API
- BM-1521 - FIX: Copy To... under Edit Button should be a Modal
- BM-1524 - FIX: Issues with very large action logs on execution details page
- BM-1527 - FIX: Purging applications with shared whole deployment plans results in a FK Constraint error
- BM-1518 - FIX: Release names with spaces will collapse white space into null too greedily
- BM-1523 - FIX: Restore equivalent to BuildExecutionPlanAction_GetVariableValues API method
- BM-1517 - FIX: Action server not updated in UI after editing an action
- BM-1516 - FIX: Workflow predicate cannot be edited
- BM-1510 - FIX: Artifact browser duplicates folders
- BM-1514 - FIX: Commonly used action links on action search page always acting like the extension is not installed
- BM-1515 - FIX: Execution-level logs should be displayed on execution details page
- BM-1513 - FIX: Links that are not enabled should be grayed out on the Admin page
- BM-1512 - FIX: Recent errors has incorrect order
- BM-1507 - FIX: Clone Application
- BM-1508 - FIX: Global deployment plans list page takes a long time to load
- BM-1509 - FIX: Uninstalled actions do not redirect to Install Extension page
- BM-1505 - Add failure, success handling options to action group level
- BM-1506 - Add UI for new execution options to deployment plan editor
- BM-1504 - Allow build number to be specified when creating a build and through triggered builds with "buildNumber" argument in query string
- BM-1428 - FIX: Do not attempt to initialize or deploy to servers in a server group that are not active
- BM-1503 - New Artifact Overview page
- BM-1496 - Add Global/Reusable Deployment Plans
- BM-1495 - Allow Action Groups to Execute in Parallel
- BM-1494 - Allow Action Groups to Iterate over Servers, Deployables
- BM-1497 - Allow Deployment Plans to Execute as Action
- BM-1499 - Redesign Execution Details Page
- BM-1498 - Share Entire Deployment Plans Across Applications
BuildMaster 4.2 - Limited Support
- BM-1487 - FIX: "All" links on Execution Details page display a blank page
- BM-1490 - FIX: Concatenate files action does not auto-detect encoding correctly
- BM-1491 - FIX: Configuration Profile Selection on Certain Actions
- BM-1492 - Include Scope Name on System Variables Listing
- BM-1489 - Make Admin Link Visible for Any Admin Task
- BM-1488 - Make it easier to search for and assign server names to server groups or environments
- BM-1486 - FIX: Possible deadlock when executing multiple remote commands against the same server at the same time
- BM-1478 - Add filter for Execution Status on the Deployment History page
- BM-1479 - Add filter for failed cases only the Unit Test Results page
- BM-1474 - FIX: [complete log] Link
- BM-1475 - FIX: [tests] link on the Execution Details page redirects to the legacy test results page instead of the newest one
- BM-1472 - FIX: Actions that send emails should assign the action's timeout setting to the SMTP client
- BM-1477 - FIX: Creating the same tutorial application results in a duplicate provider error
- BM-1481 - FIX: Environment-server selection should freely allow any server to be a part of an environment instead of forcing local agents to be included
- BM-1482 - FIX: Give more space on All Release's page filter bar for the manage sequence checkbox
- BM-1480 - FIX: Server group link on the Environment Overview page assumes the item is a server instead of a server group
- BM-1483 - FIX: Setting a release or promotion-level variable from the Set Variable Value action will create a new execution variable instead of actually mutating the value of the existing variable
- BM-1476 - FIX: Unit Test History page should be updated to use new filter
- BM-1473 - FIX: Variable servers with bracket syntax are not escaped properly
- BM-1471 - FIX: Configuration file secured task validation error
- BM-1470 - FIX: Reexecuting a failed reexecution in the final environment causes a constraint error
- BM-1463 - Add $Increment and $Decrement functions
- BM-1454 - Do not allow invalid characters when creating variables
- BM-1468 - Extension configuration profile property summary should not display encrypted values
- BM-1462 - FIX: $ExecutionUser function returns execution ID instead of user name
- BM-1458 - FIX: Connection error on database connection page for some database providers proxied to SOAP agents
- BM-1460 - FIX: Connection error when displaying very large change script histories
- BM-1459 - FIX: Copying action groups to a new environment in the same application can cause odd behavior
- BM-1464 - FIX: NullReferenceException when creating or editing an action where there is a server that the current user does not have access to
- BM-1455 - FIX: Predicates sometimes listed twice on deployment plans
- BM-1466 - FIX: Server details page does not have a title
- BM-1469 - FIX: TCP agent sometimes fails to restart after an update on Windows Server 2003
- BM-1467 - FIX: Text box validation error appears at the top of modal pages instead of next to the offending text box
- BM-1465 - FIX: Unknown escaped variables are sometimes replaced with unescaped variables
- BM-1461 - FIX: Upgrade checklist link remains visible even if everything has been marked complete
- BM-1456 - FIX: Variable Predicate should allow function names
- BM-1457 - Function names should be minimally escaped on action help page
- BM-1452 - FIX: Cannot find instance name error when saving a Deploy Configuration File action
- BM-1451 - FIX: Duplicate instance names may appear in DeployConfigFileAction instance name dropdown
- BM-1453 - FIX: Execution-time variables are not getting replaced in Deploy Configuration File actions even if the box is checked
- BM-1448 - FIX: Incorrect error displayed when testing a database provider
- BM-1446 - FIX: Long action descriptions cause truncation issues
- BM-1449 - FIX: Reexecution doesn't include sensitive variables
- BM-1447 - FIX: Replace Text action should truncate description for long replacements
- BM-1450 - Make custom ProviderBasedActions compatible with pre-4.2 extensions
- BM-1443 - Add PathCombine variable function
- BM-1442 - Allow service to start without database access
- BM-1444 - Display source application for imported deployables in deployment plans
- BM-1400 - FIX: bmservice.exe should return nonzero exit code if service installation fails
- BM-1438 - FIX: Broken links on some admin pages
- BM-1441 - FIX: Create Release page restricts permission even for users with Releases_ManageRelease for a specific application
- BM-1445 - FIX: Delete button on change controls overview page should be right-aligned
- BM-1436 - FIX: Deploy Config File action description doesn't highlight target directory
- BM-1435 - FIX: Variables not getting replaced in source or target directory properties
- BM-1437 - Improve UI on create/edit built in users & groups pages
- BM-1439 - Small UI style tweaks on some admin pages
- BM-1421 - Add classes for providing a more detailed action description
- BM-1429 - Add Create New Release action
- BM-1351 - Add link to LDAP documentation on LDAP config page
- BM-1432 - Automatic BuildMaster registration in agent installer
- BM-1431 - Automatic Windows agent type detection for new servers
- BM-1399 - Automatically create working directory for execute command line action if necessary
- BM-1395 - Change action server picker to server selector used in transfer files action
- BM-1412 - Describe what is copied on clone application page
- BM-1405 - FIX: Actions that succeed after a number of retries can still mark an execution as failed
- BM-1406 - FIX: Application navigation bar should not appear on all applications page
- BM-1409 - FIX: Automatic activation of existing license key on new install does not work
- BM-1415 - FIX: Copying or linking an action group when there is only a single deployable in an application will incorrectly associate the new group with "all deployables"
- BM-1402 - FIX: Edit built in user page always selects all groups
- BM-1403 - FIX: Hidden items in application navigation menu will duplicate borders even if the menu options are missing
- BM-1410 - FIX: Import/Export deployment plan button is displayed even without privileges to use it
- BM-1386 - FIX: Move add action hover menu up by one pixel
- BM-1417 - FIX: System Overview Active Releases gadget displays incorrect build number for environment (uses what appears to be furthest bld #, but correct exec time)
- BM-1419 - FIX: Unit Test Results page does not convert test start and end times to UTC correctly
- BM-1408 - For selection of deployable when adding a change script if application has multiple deployables
- BM-1414 - Imported deployment plans should retain linked groups
- BM-1433 - Improve performance for editing large deployment plans
- BM-1420 - Improve support for cancellation of remote commands
- BM-1434 - Improved dropdown for provider-based actions
- BM-1416 - Increased robustness for provider proxies
- BM-1211 - Inheritable servers for actions and action groups
- BM-1401 - INSTALLER: Allow period character in the database name from a manually-entered connection string
- BM-1430 - New $variable syntax for applications
- BM-1392 - Re-align "Update All Extensions" button
- BM-1396 - Show environment heading on application overview page
- BM-1404 - Workflow details and policies should be ordered the same on the edit page as they are on the overview page
BuildMaster 4.1 - Limited Support
- BM-1427 - FIX: Incorrect privilege validation for servers, specifically the View_Server task
- BM-1426 - FIX: SSH Agent compatibility with IBM AIX servers
- BM-1424 - FIX: Application picker can display blank application names when the application is part of a group
- BM-1418 - FIX: Privileges for Deployment Plans, Database Connections
- BM-1398 - FIX: TCP agents do not accept commands while executing a process
- BM-1397 - FIX: Variables should not be displayed to users in the action log unless ViewDebugLogs privilege is granted
- BM-1381 - Allow users to specify an alternate connection string for upgrades
- BM-1394 - FIX: Builds_ViewExecutionDetails should be scopeable by application
- BM-1390 - FIX: Create variable page throws a SecurityException when privilege is scoped by application
- BM-1385 - FIX: Modified date on Plans table is not updated when actions are edited
- BM-1382 - FIX: On the Change Scripts table, Ajax rendering does not update after save
- BM-1389 - FIX: Promotion Requirement status should only be checked asychronously on the build overview page
- BM-1387 - FIX: Release Notes Gadget does not use partial render for adding release notes
- BM-1374 - FIX: Cloning an application with a scoped promotion variable results in a check constraint error
- BM-1379 - FIX: Compare Directories report has broken links when files with differences have a space in the name
- BM-1373 - FIX: Deploy All Config Files action displays duplicate instance names in dropdown
- BM-1375 - FIX: Deployment plans should indicate target server for Transfer Files actions
- BM-1378 - FIX: Edit variables page privileges should be scoped to application when appropriate
- BM-1380 - Hide passwords from clients when UseDpApiForPasswords is enabled
- BM-1376 - Transfer Files action editor should show (default) as default path
- BM-1365 - Allow null Environment_Id for build artifacts
- BM-1371 - Allow release resequencing regardless of release count selected
- BM-1368 - Application picker should display application groups on clone application page
- BM-1359 - FIX: Add download link on updates page and fix styling
- BM-1369 - FIX: Clone application does not propagate configurer profile or transfer files targets for unlinked action groups
- BM-1361 - FIX: Create and close release triggers should not log an error just because an application does not have an associated issue tracker
- BM-1372 - FIX: Deploy release button does not appear with one environment in a loose workflow
- BM-1366 - FIX: Execute script base action should combine script file path with source directory
- BM-1360 - FIX: Imported deployable release dropdown should not include canceled releases
- BM-1356 - FIX: Installer crashes trying to update IIS settings on Windows Server 2012
- BM-1364 - FIX: ModalHeight on action editor page should not be greater than viewport size
- BM-1358 - FIX: Possible TypeInitializationException with invalid activation code
- BM-1367 - FIX: Release deployables dropdowns should have release name instead of release number
- BM-1352 - FIX: Transfer Files action does not allow variable servers
- BM-1363 - Providers_GetProvider should not throw an error if the provider was not found
- BM-1353 - FIX: Create File action should not write byte order marker by default
- BM-1355 - FIX: Link to server group details page is broken
- BM-1354 - FIX: Variables not being replaced in PowerShell scripts that are embedded in actions
- BM-1295 - Add "output to file" option to execute client command
- BM-1306 - Add create new issue button to release page for supported issue trackers
- BM-1347 - Add detailed error message to server page
- BM-1342 - Add MAJORVER, MINORVER, and REVISIONVER variable values
- BM-1348 - Add output parameters to JSON API return methods
- BM-1199 - Add UseDpApiForPasswords configuration option
- BM-1332 - Allow Execution variables to be entered on the Create Build page
- BM-1334 - Allow HTML in issue tracker descriptions
- BM-1336 - Built-in script library
- BM-1339 - Change FormsAuth cookie name to BMXAUTH to prevent conflicts with ProGet
- BM-1337 - Connections to remote resources should be proxied through the service if possible
- BM-1345 - Exported plans do not contain deployables for action groups
- BM-1341 - FIX: After purging an application, the redirect to admin page fails in certain browsers with an "Application does not exist" message
- BM-1349 - FIX: Application group scoped privileges
- BM-1325 - FIX: Display error for promotion requirements that cannot be loaded because of configuration errors
- BM-1340 - FIX: Purge Artifacts trigger can fail if configured to delete immediately upon build rejection
- BM-1344 - FIX: Set Variable Value from File does not override higher-scoped variables
- BM-1343 - FIX: TargetInvocationException is not unwrapped when testing providers on remote servers
- BM-1168 - Limited-User Licenses Clarification
- BM-1335 - Remove upgrade links from within the Express edition and replace with minimizable mentions of Enterprise edition
- BM-1308 - SDK: Add ability to use a custom icon URL in a custom extension
- BM-1298 - Unit Test reporting improvements
- BM-1350 - Update Environments page to include breadcrumb and show servers as blocks instead of table layout
- BM-1346 - Variable Predicate improvements
BuildMaster 4.0 - Limited Support
- BM-1326 - Add option to not log warning when there are no scripts to execute
- BM-1317 - Add server errors list to server overview page
- BM-1328 - Allow deployable to be selected when generating changescripter
- BM-1330 - Do not assign default release name when editing a release
- BM-1321 - FIX: Change Server Type recipe should skip agents that can't be deserialized
- BM-1324 - FIX: DATE,DATE2 variables are always in UTC now and always refer to the execution start date instead of the current date
- BM-1327 - FIX: Execution Status predicate should not fail with warnings
- BM-1329 - FIX: Log Errors as Warnings stills logs as an error for legacy actions
- BM-1322 - FIX: Providers should be in alphabetical order and not allow duplicate names
- BM-1320 - FIX: Use release name as alias on included deployables
- BM-1319 - FIX: Windows extension should not be deleted on upgrade
- BM-1323 - Show loaded extension components on extension details page
- BM-1304 - Add "Back to Servers" link on Server Overview page
- BM-1309 - Add schedule name and application name to SCM trigger error log entries
- BM-1296 - Allow use of a Variable in ManualAction for Username
- BM-1307 - API: Release_PurgeReleaseData method does not account for build execution variable values
- BM-1302 - Application Group selecter should be an auto-complete textbox instead of a dropdown to allow for new values to be entered
- BM-1305 - Create New Release option can still be visible even if Multiple Active Releases are disabled
- BM-1293 - Do not try to prepare Inactive servers for an execution
- BM-1312 - FIX: Admin link should be hidden when the specific "Admin_Configure" privilege is denied for a user, even if the user can do other administrative tasks
- BM-1315 - FIX: Cannot add promotion variables when creating a build (and promoting to the first environment)
- BM-1301 - FIX: Create New Build action fails when creating a build for all dependent applications
- BM-1303 - FIX: Custom Error Page is not displayed when there is an unhandled exception which results in an error code of 500
- BM-1294 - FIX: Custom proxy configuration will fail when the Proxy_BypassUrls value is set to an empty string
- BM-1291 - FIX: Edit change script page does not populate release number or deployable fields with correct values
- BM-1297 - FIX: Error When Re-saving Required Promotion Variables
- BM-1311 - FIX: Intermittent error using shared SSH key file
- BM-1314 - FIX: Manual action would send emails to users not in a specified group when the principal assigned is a group
- BM-1310 - FIX: Privilege denials are ignored when the privilege itself is not scoped to an application or environment
- BM-1299 - FIX: Recipe pages that use an ApplicationPicker require an updated version of jQuery
- BM-1149 - FIX: Transaction error when supplying a Group name to a User approval
- BM-1316 - FIX: Unique key violation when attempting to create a build with two promotion or execution variables scoped to different environments with the exact same name
- BM-1267 - FIX: Unit test reports are not displayed unless build is in assigned environment
- BM-1300 - FIX: Update BuildMaster extension recipes with sample code and support for .NET 4.0
- BM-1313 - FIX: When cloning an application with a single hidden deployable, the setup release does not include that deployable
- BM-1290 - Add appropriate @media print style for execution log output
- BM-1277 - Clarify workflow policies
- BM-1289 - FIX: BinaryDataProcess throws ArgumentException for certain valid sets of input data
- BM-1270 - FIX: Clone application does not work for some applications
- BM-1273 - FIX: ComboSelect does not post back on value change in Chrome or Firefox
- BM-1281 - FIX: Database providers not logging output messages on BuildMaster server
- BM-1272 - FIX: Delete image does not look clickable on imported deployables list
- BM-1283 - FIX: Deleting a server used by the "target server" of a transfer files action in a deployment plan will fail
- BM-1271 - FIX: Import deployable always imports first deployable in list regardless of selection
- BM-1274 - FIX: Invalid activation codes are not considered license errors
- BM-1279 - FIX: Missing "X" on some modal dialogs
- BM-1269 - FIX: Missing icons for Create New Application wizards when not connected to the Internet
- BM-1282 - FIX: Selecting an issue tracker that is improperly configured results in a vague error message when the provider is assigned to an agent
- BM-1288 - FIX: SSH connections are not being immediately closed after an SSH action completes
- BM-1286 - FIX: Viewing a configuration file from the overview page throws an exception when the version number is missing
- BM-1276 - Log Command Line Arguments should only be displayed by default for source control providers
- BM-1278 - Remove extra "X" from the action search box in IE
- BM-1287 - Servers set to "Inactive" will show up as the last status they were in before marked inactive
- BM-1252 - Add button to update all extensions
- BM-1266 - BuildMaster service should wait for SQL Server availability on startup
- BM-1259 - FIX: API key setting is only available when upgrading from a pre-4.0 version
- BM-1256 - FIX: Deleting a named user deletes the last user in the list
- BM-1258 - FIX: Environments are sometimes displayed in the wrong order on the all applications page
- BM-1233 - FIX: Firefox not rendering smallediticon.svg correctly
- BM-1255 - FIX: Non-scoped tasks are incorrectly denied along with scoped tasks
- BM-1265 - FIX: Register New Database button shows error page if there are no database providers in any extensions
- BM-1262 - FIX: Remote process execution using SSH agent does not work on certain configurations
- BM-1249 - FIX: Selecting a configuration file instance to preview before any other dropdowns will yellow screen
- BM-1254 - FIX: Service installation should grant the "log on as service" privilege when necessary
- BM-1261 - FIX: Specified cast is not valid exception when running attempting to run an approval required notifier when there is no "next environment"
- BM-1257 - FIX: Transfer files action does not persist server IDs correctly across postbacks for the button on the file picker
- BM-1260 - FIX: Upgrade checklist still shows there are extensions errors even if they've been resolved
- BM-1263 - When adding a new action, selecting a tag should filter by that tag only instead of ANDing the search result with another selected tag
- BM-1247 - FIX: Installer fails when using LocalSystem as service account
- BM-1251 - FIX: Manual action notifier needs to be updated for new 4.0 style
- BM-1250 - FIX: Powershell script output is not logged on SOAP agents
- BM-1248 - FIX: There should not be a legacy dropdown displayed with 5 or more configuration file instances in the edit window - just show them all
- BM-1243 - Add workflow policies which include the ability to deploy to any environment in the workflow and auto-release creation/cancellation/closing options
- BM-1239 - FIX: Agent installer maps IIS site root to TargetPath instead of BinPath
- BM-1234 - FIX: Creating a build of a release assigned to a workflow with no steps will yellow screen
- BM-1237 - FIX: Events links do not pop up in a modal page
- BM-1241 - FIX: Execution completion notifier gives warning if user doesn't exist
- BM-1238 - FIX: Extension gallery overview page display a yellow screen if there is no connection to the internet from the BuildMaster server
- BM-1244 - FIX: Installer should change app pool managed runtime version to 4.0 on upgrade
- BM-1240 - FIX: Many minor bug fixes, see the BuildMaster 4.0 Beta notes knowledge base article for more information (http://inedo.com/support/kb/1067/buildmaster-40-beta-notes)
- BM-1242 - FIX: Re-execute from last failed action now includes WarningIndicator when copying logs to new execution
- BM-1245 - Releases are no longer automatically sorted by their release number and can now be sorted manually by the user
- BM-1205 - Rename Release History page to All Releases page, and allow sorting by included release deployable
- BM-1235 - Update approvals gadget to show approvals for all environments if workflow is set to allow promotions to any environment
- BM-1221 - Application Dashboard
- BM-1231 - FIX: APPDIR, WRKDIR, and ROOTDIR variables not replaced in source or target paths for actions
- BM-1192 - FIX: Downloaf Artifact WebUI Truncates Name in Some Browsers if ARtifact has a Space
- BM-1232 - FIX: Odd workflow behavior when unrun predicate is involed in last action group
- BM-1194 - FIX: Predicate not Evaluated if First Action in Group is Uninclused
- BM-1219 - Tweak Server Page UI
- BM-1225 - Allow Variable Declaration on Definition Pages
- BM-1220 - BuildMaster Overview Dashboard
- BM-1175 - Change behavior of Automatic Builds to queue up builds if there are SCM changes detect, and do not attempt to determine changes when there are executions in the queue
- BM-1191 - Expand Artifact search to check for the most appropriate first (matching release deployable, imported deployable, etc.) then expand to artifacts associated with other deployables or "all deployables"
- BM-1010 - FIX: TCP Agent host service terminates when it receives an incorrect security token
- BM-1206 - FIX: Variable-based Promotion Requirement assumes Promotion-level scoping for a variable as its most specific, when it should be Build-level scoping
- BM-1229 - FIX: Variables not replaced in Working Directory property of Execute Command Line action
- BM-1227 - Long action descriptions on the Execution Details page should not increase the size of the containing table and push text off the screen
- BM-1224 - Remove API Key Page, use All Settings to update the API key instead
- BM-1230 - Update Logon Page
- BM-1197 - Allow Database Connection from Other Environment to be Used in Database Actions
- BM-1213 - Allow dates and times to be displayed in the current user's format and time zone
- BM-1216 - Consolidate "Create New Action Group" and "Copy/Link Action Group" buttons into a type picker
- BM-1217 - Deemphasize Promotions
- BM-1160 - Don't allow promotion of builds to first environment when there are approvals/reqs
- BM-1204 - FIX: Edit variable values should not be displayed on edit release page
- BM-1207 - FIX: UTC Time Displayed on View Error Page
- BM-1214 - Implement a DeployConfigurationFileActionBase
- BM-1215 - Import/Export of Deployment Plans
- BM-1212 - Prepare agents for execution asynchronously
- BM-1200 - Role tasks defined as "non-scopable" should not apply any application or environment-level scoping when determining if a user has privileges
- BM-1162 - Separate Server Groups on Server Page
- BM-1208 - Set ServerID when Logging Agent-based Issues
- BM-1161 - Add "OFF" status to Servers
- BM-1147 - Add "Reject All Active Builds" Button to Edit Release
- BM-1203 - Add BuildMaster 4 Upgrade Checklist
- BM-1143 - Add ComboBox Control
- BM-1152 - Add Create Release Note action
- BM-1145 - Add multiple workflows to the application navigation bar
- BM-1185 - Add Set Variable from File action
- BM-1202 - Allow CommandLineAction To export BuildMaster Variables
- BM-900 - Change ReleaseNumber Sorting
- BM-1182 - Database Action Logging Improvements
- BM-1170 - Database/ChangeScripts UI Tweaks
- BM-1156 - Display current directory provider on log in page
- BM-1150 - Display release name instead of number when not empty
- BM-1153 - Do not display "Reject Current..." on Create New Build w/o MultipleActive Builds Enabled
- BM-1177 - Edit Release page should explain why workflows can't be changed when the dropdown is disabled
- BM-1178 - FIX: Can edit canceled/deployed releases by entering release number in the create release page
- BM-1179 - FIX: Can set variable values for a deployed release
- BM-1180 - FIX: Cannot set variable to non-default value directly on Create New Release page
- BM-1181 - FIX: Reject Current Build in First Environment checkbox is always disabled on Create Build page
- BM-1163 - FIX: Spacing on Server Overview Page
- BM-901 - FIX: URL-trigger build with basic authentication does not work with integrated web server
- BM-1146 - Have Add Promotion Requirement Page display as modal
- BM-1151 - Hide "Deployables" Concept When Only 1 Deployable
- BM-1190 - Hide provider type field on Download Change Script Deployment Tool page unless there are at least two
- BM-1186 - HTTP actions should be in BuildMasterExtensions
- BM-1189 - Improve Compare Directories Report action
- BM-1090 - Improve integrated web server configuration from command line
- BM-1173 - Improve UI Validation Errors w/ Custom Validator Styling
- BM-1184 - Install Service with "Auto Recover"
- BM-1157 - Log ServerId when AgentUpdate is Unable to Connect to Server
- BM-1155 - Log warning message when capturing empty artifacts
- BM-1171 - New Filter String Controls
- BM-1166 - Proxy settings page should be modal
- BM-1069 - Refactor the Execution In Progress Page
- BM-1172 - Remove History Links from Main Application Navigation
- BM-1169 - Rename CoreEx Configuration Values
- BM-1165 - Restart Service When Changing Proxy Configuration
- BM-1144 - Rewrite Create New Application Page
- BM-1196 - Silent Agent Installation
- BM-1193 - SMTP settings page should be modal
- BM-1154 - TimePicker Control
- BM-1095 - Upgrade JQuery, remove Wijmo controls
- BM-1167 - Web/Service Restart Control