How does one leverage Bluemix Service - Active-Deploy (Beta) within Delivery Pipeline ?

Currently Delivery Pipeline Deploy Job constantly updates same application App-001 with new changes based on new builds.

Active-Deploy Service in Bluemix talks about deploying App-001 and then when new version is built it talks about deploying App-002 without route and then using active-deploy cli to move traffic from App-001 to App-002 and so on and so forth.

How do we use this zero-downtime deployment capability of Active-Deploy within the delivery Pipeline ?

Would Delivery Pipeline be used in Dev/QA cycles and to deploy to PROD , active-deploy CLI would be leveraged outside of hub.jazz.net?

1 reply

Sorry for the delay on this - I recently took over the offering management position from Carl Swanson on Active Deploy. There is a good blog Carl wrote back in March about using AD with the Pipeline support specifically: