• Support for multiple buildpack in Cloud Foundry manifest files
• Support for Bamboo 7.x

In rare circumstances, some users were experiencing timeout exceptions. This release fixes that issue.

• Added support for "health-check-http-endpoint" in the manifest
• Upgraded the version of the cf-java-client used by the plugin to get bug fixes and performance improvements

• Upgraded to the latest Cloud Foundry client for performance and stability improvements
• Added support for 'process' and 'http' health check types
• Fixed CFBAMBOO-232 - Unable to save Application Task with List Applications option
• Fixed CFBAMBOO-236 - Unable to push an app that has previously failed to stage due to "CF-StagingError(170001): Staging error: cannot get instances since staging failed"

The latest version should bring some bug fixes and stability improvements.

New Features

• Support for binding route services
• One-off task logs are streamed back as Bamboo logs when waiting for a task to complete

Bugs Resolved

• CFBAMBOO-217 - CF Push does not support route-paths

Upgraded to cf-java-client 2.4.0.RELEASE. This brings many improvements including:

• Fix for CFBAMBOO-209 - CF Push task unable to push apps that have the application location to utilize the directory
• Application upload speeds should be dramatically improved as the cf-java-client now uses the "resource matching" endpoint to determine what files need to be uploaded rather than uploaded all files every push.

Support for Cloud Foundry One-off Tasks:

• A new Bamboo task has been added for running one-off tasks.
• A task workflow option to wait for a one-off task to complete before proceeding with the build or deployment.
• One-off task support is currently considered beta so please provide feedback.

New features and Improvements:

• Support configuration of Staging Timeout in Push task
• Startup Timeout in Push task s now be optional and defaults to values like the CF CLI
• All task configuration options now accept Bamboo parameters
• Internally, upgraded to cf-java-client 2.3.0.RELEASE
• [CFBAMBOO-214] - Remove temporary workaround for cf-java-client invalid credentials issue

Bug Fixes:

• [CFBAMBOO-210] - Startup timeout in push task is not respected
• [CFBAMBOO-212] - In the Push task config, the health check timeout is incorrectly labeled as "startup timeout"

IMPORTANT NOTE: This plugin version requires version 235 or greater of Cloud Foundry.

New Features:

• [CFBAMBOO-167] - Add syslog drain and route service URLs as an options to the User Provided Service Task

Bug

• [CFBAMBOO-194] - Unable to push app: null after upgrade to 3.x - Fixed an issue affecting large applications

New Feature and Improvements

• [CFBAMBOO-131] - Update description of "time to wait before failing" field in push task to indicate it is equivalent of CF_STARTUP_TIMEOUT
• [CFBAMBOO-205] - Remove experimental tag from blue/green deployment option
• [CFBAMBOO-184] - Push task reset stale user provided environment variables should be configurable
• [CFBAMBOO-165] - Support no-hostname attribute in manifests
• [CFBAMBOO-198] - Support a no-hostname flag in Push manual task configuration

Bugs

• [CFBAMBOO-196] - 'Unable to push app: Domain io does not exist' when route is at domain's root
• [CFBAMBOO-199] - CF Push fails because the domain does not exist
• [CFBAMBOO-204] - Application Stop Task not working

Improvement

• [CFBAMBOO-195] - Map/unmap routes serially instead of concurrently to work around concurrency issue in Cloud Controller - CF-DatabaseError(10011)

Bug

• [CFBAMBOO-185] - Create User Provided Service Task fails in some Bamboo deployments
• [CFBAMBOO-186] - In App rename task, failIfAppDoesNotExist does not work

Improvement

• [CFBAMBOO-181] - Blue/Green config logging shouldn't log "null" but rather a blank
• [CFBAMBOO-187] - User Provided Service task configuration should accept bamboo parameters
• [CFBAMBOO-188] - Application task configuration should accept bamboo parameters
• [CFBAMBOO-189] - Routing task configuration should accept bamboo parameters
• [CFBAMBOO-192] - Log health check success in blue/green deployments

• CFBAMBOO-183 - Routes with underscores cause an IllegalArgumentException
• CFBAMBOO-182 - Improved logging during error scenarios

Resolved issue with blue/green deployments where deployment would fail if "live app" did not previously exist.

Enhancements to Blue/Green Deployments

• CFBAMBOO-176 - For blue/green deployments, the app name and routes in the manifest (or task config) should be used for the live app
• CFBAMBOO-177 - Support mapping multiple routes from within a blue/green deployment

General Updates

• Upgraded to the latest version of the cf-java-client
• CFBAMBOO-168 - Delete option on the application task should not fail if the app does not exist

• Fixed CFBAMBOO-170: Unable to run deployment on existing CF Push tasks after upgrade without re-saving task config.
• Updated the blue/green deployment configuration options in the Push task
• Added a health check option to the blue/green deployment

• Routes with paths are now supported in the Push Task config, map/unmap functions in the Applications Task, and create/delete routes function in the Routes Task.
• Manifest files now support the new "routes" attribute and support routes with paths
• Multiple domains are support in manifest files
• no-route attribute is supported in manifest files
• Deprecated 'urls' attribute in manifest in favor of 'routes'
• Renamed "URL" to "Route" in the task configuration UIs to be consistent with Cloud Foundry terminology
• health-check-type attribute is supported in manifest files

• Updated to the latest version of the cf-java-client
• Improved error handling

• Upgrade to new cf-java-client v2: The internals of the plugin have been rewritten to use the new v2 of the Java client. This provides more effective interaction with the Cloud Controller and will make it easier to add new features going forward.
• Staging and app logs now streamed back to Bamboo and available in the deployment logs
• The log output of the plugin now closes matches that of the CF CLI to provide a more consistent and familiar experience
• A blue/green deployment option has been added to the Push Task.
• The "Service Push" task now supports updates.
• In the Service Task, the configuration options for "create service" changed from a drop down to text fields.
• The values of environment variables are now redacted any time they are written to the logs to avoid exposing any sensitive data.
• The gadgets have been removed from the plugin.

Due to the inner workings of the cf-java-client, you may need to increase the max heap size for your agents.

New Feature

• [CFBAMBOO-140] - Support task specific CF environment configuration
• [CFBAMBOO-142] - Experimental Service Push Task

Improvement

• [CFBAMBOO-139] - Change "Target" to "Environment" in all text
• [CFBAMBOO-141] - Update Cloud Foundry Logos

New Feature

• [CFBAMBOO-73] - Memory is now optional in the API. Will default if not provided
• [CFBAMBOO-75] - Stacks are now exposed through the API
• [CFBAMBOO-129] - Support disk_quota attribute in manifest

Task

• [CFBAMBOO-136] - Deprecate 'mem' attribute in manifests

Improvement

• [CFBAMBOO-130] - For manifests, either make the minimum required fields the same as the CLI or improve UX for validation errors
• [CFBAMBOO-135] - When a 'path' is specified in a manifest, issue a warning in the build logs
• [CFBAMBOO-137] - Memory attribute in manifest should support unit

Bug

• [CFBAMBOO-132] - disk has been changed to disk_quota in standard manifest file format
• [CFBAMBOO-134] - App disk quota must be greater than zero

Improvement

• [CFBAMBOO-125] - Support both url and urls for the list of URLs in a manifest
• [CFBAMBOO-126] - Upgrade cloudfoundry-client-lib to >= 1.1.1

New Feature

• [CFBAMBOO-124] - Support for multiple hosts in manifest files

Story

• [CFBAMBOO-117] - As the CF admin I should be able to configure which targets are available to Build Plans

Task

• [CFBAMBOO-118] - Remove StartupLogFetcher that originally printed out staging and app logs during startup

Improvement

• [CFBAMBOO-110] - Manifest Parsing: When a host is provided without a domain, the platform domain should be used.
• [CFBAMBOO-112] - Improve performance of "applicationExists" method
• [CFBAMBOO-114] - Improve performance of "serviceExists" method

New Feature

• [CFBAMBOO-108] - Attributes defined outside the application block in the manifest should be available for symbol resolution

• [CFBAMBOO-34] - Use Bamboo Variables in manifest file symbol resolution

Bug

• [CFBAMBOO-107] - Push task throws a NullPointerException in the get status code when "wait for app to start" is not checked

Improvement

• [CFBAMBOO-101] - Update logging in Service Task
• [CFBAMBOO-103] - The push task should write the status of an app (if it exists) before the push activities begin and then again at the end of the push

New Feature

• [CFBAMBOO-100] - During a push services no longer configured should be unbound from the app

Task

• [CFBAMBOO-87] - Update in-task help screen for manifest formats to include disk quota and timeout

Bug

• [CFBAMBOO-105] - Routing Task Config not displaying heading text correctly
• [CFBAMBOO-106] - The rename app action should have a option to not fail if the app to rename doesn't exis

New Feature

• [CFBAMBOO-76] - A healthCheckTimeout can now be set on Staging

Both manual configuration and manifest configuration are supported. This feature is equivalent to the -t option on the cf CLI.

Improvement

• [CFBAMBOO-97] - Reintroduce the custom multiple URL attribute in manifest parsing removed for v2

• [CFBAMBOO-95] - Upgrade cloudfoundry-client-lib to version 1.0.3
• [CFBAMBOO-96] - Trusting of self-signed certs is not being applied to the REST API

New Feature

• [CFBAMBOO-92] - Support service binding in manifest files where only the service name is provided for pre-existing services.

Bug

• [CFBAMBOO-93] - A number in the version field for a service in manifest.yml causes a casting issue.

Bug

• [CFBAMBOO-91] - Could not read JSON: Can not construct instance of... Exception in Bamboo 5.5.x

• [CFBAMBOO-88] - "java.sql.SQLException: Session is closed" when plugin is used in a Scheduled or After successful build plan triggered deployment

• [CFBAMBOO-88] - "java.sql.SQLException: Session is closed" when plugin is used in a Scheduled or After successful build plan triggered deployment

Improvement

• [CFBAMBOO-44] - Remove runtime and framework tabs from Target view
• [CFBAMBOO-45] - Service Task: update for Cloud Foundry v2
• [CFBAMBOO-50] - Update REST services for new formats in v2
• [CFBAMBOO-51] - Update manifest.yml parsing for v2 format

New Feature

• [CFBAMBOO-43] - Push Task: Update for Cloud Foundry v2
• [CFBAMBOO-47] - Application Task: update for Cloud Foundry v2
• [CFBAMBOO-53] - Application Task: Add support for the CF rename command
• [CFBAMBOO-57] - Add map-domain and unmap-domain capabilities to a Task
• [CFBAMBOO-58] - Add add-route and delete-route capabilities to a Task

Task

• [CFBAMBOO-54] - In the Target dashboard, update the Services and Provisioned Services for new format
• [CFBAMBOO-55] - Remove Cloud Controller Version from Target dashboard

New Feature

• [CFBAMBOO-39] - Support deployment tasks in Bamboo 5

Improvement

• [CFBAMBOO-11] - Use the new RuntimeTaskDataProvider to provide centrally stored data to remote Tasks at runtime
• [CFBAMBOO-42] - All keys in the TaskDefinition config map should have a Cloud Foundry prefix to avoid conflicts with other form elements

Bug

• [CFBAMBOO-40] - NullPointerException when configuring some options on a ServiceTask

Cloud Foundry for Bamboo Plugin - Version cloudfoundry-plugin-1.2

Bug

• [CFBAMBOO-24] - URLs should not be required for Push Tasks
• [CFBAMBOO-36] - Using the ${target-base} symbol in a manifest file always results in api.cloudfoundry.com

Improvement

• [CFBAMBOO-33] - Manifest file symbol resolution should apply to all relevant fields and values

Story

• [CFBAMBOO-37] - Task to lookup app name and set it as a Bamboo Job variable

Cloud Foundry for Bamboo Plugin - Version cloudfoundry-plugin-1.1

Bug

• CFBAMBOO-32 - The Push task JavaScript error messages aren't being pulled in from i18n files
  

Improvement

• CFBAMBOO-31 - When a user selects a Cloud Foundry task and there are no configured Targets, a message should be displayed indicating that admins need to add targets
• CFBAMBOO-35 - If there haven't been any deployments, the Recent Deployments section of the dashboard should display a message box indicating such\

Story

• CFBAMBOO-22 - A new admin user should be guided through the process of configuring a new Target