CA Continuous Delivery Director 6.7 General Availability Announcement

3895

01 May 2018

01 May 2018

Date:   May 01, 2018

We are excited to announce the release of version 6.7 with many new and improved features. We have added several integrations that help to connect the DevOps tools and create a complete, automated pipeline. In addition, you’ll see several improvements to the design and execution of releases. These capabilities will improve the productivity of the team responsible for the release, and the quality of the changes.

What’s new in 6.7?

Rerun failed task

This new feature allows users to skip or rerun a specific task. This is extremely efficient, especially when running tasks like deployments or tests. Upon failures, the users can investigate the root cause, mitigate the issue, and easily rerun the operation to ensure success. Customers have often requested this capability, and we are happy to deliver.

Schedule a recurring phase

This feature allows users to easily schedule a recurring execution of a specific phase in CDD. This helps when CDD is connected to a CI system, and on a specified schedule (for example, every night) a pipeline should be initiated and the release should execute. 

Figure 1

 

Sign-up with custom email (SaaS)

CA Continuous Delivery Director SaaS (cddirector.io) now provides the option to sign up with your custom email. Existing sign up/sign in methodologies are still active: sign up with Google, GitHub, and sign in with organizational account (SAML).

The new sign up/sign in process offers an improved look and feel, as well as a progressive approach that minimizes sign-up friction. (Thank you everyone for your feedback!)

Figure 2

Figure 3

 

New and improved integrations

TFS Plug-in

The new integration supports seamless integration between CDD and Microsoft Team Foundation Server and provides the following capabilities:

  • Associate work items with a release to improve visibility of the content being delivered in a release
  • Automatically update work item status from release pipeline execution

Using the TFS plug-in will help users to connect CDD and TFS for a complete automated CI/CD pipeline.  Get more information on the Integration Hub.

Figure 4

REST (Improved)

The ‘REST’ plug-in allows users to create custom integrations to third-party solutions. This plug-in provides a generic integration when a custom plug-in currently is not supported.

The new version supports the following capabilities:

  • Get REST progress updates by providing equivalent ‘get status’ API
  • See progress of execution directly in the CDD UI

Get more information on the Integration Hub.

 

Figure 5

Jenkins Plug-in (Improved)

The existing Jenkins plug-in has been widely adopted by many CDD customers and allowed them to connect CDD with Jenkins. The new version come with several new capabilities based on feedback we received:

  • Support Jenkins job execution from within the release pipeline
  • New plug-in option that resides in CDD, which starts a build and subsequent pipeline execution upon approval initiated in CDD
  • Customers can choose Jenkins integration residing in Jenkins or CDD

Figure 6

ServiceNow Plug-in (Improved)

Many users of CDD are using ServiceNow, and they have been using the existing integration to update tickets in ServiceNow directly from within pipeline execution.

We have improved the plugin to increase visibility of the tickets being delivered, and now they can be mapped to a given release (like working items from Agile Central, Jira and others).

 

Figure 7

TeamCity Plug-in

Many of our users are using TeamCity as their CI solution. For that purposed, we have built a custom plug-in that allows automating the flow between TeamCity and CDD for the following use cases:

  • Support TeamCity job execution from within the release pipeline
  • Support triggering release execution upon completion of a build in TFS

Figure 8

OpenShift Plug-in

A lot of CDD users have standardized on OpenShift as their container-based platform. For that purpose, we have built a custom plug-in that helps these teams to automatically deploy to an OpenShift environment, during a release process.

 

Figure 9

For more information about this release, including any updates made after this announcement, refer to the release notes section of the documentation.

Download your on-premises version of Continuous Delivery Director 6.7 from CA Support Online. All enhancements are available in CDDirector.io now. Sign up for the SaaS version with a freemium tier level, here: http://cddirector.io

Helpful resources

CA provides resources to help you in the form of education, product documentation, community user group environments, and experienced support personnel:

  • Access CDD Learning Paths for educational offerings.
  • Access the Continuous Delivery Director online community to connect, learn, and share with other users in a collaborative online environment.
  • Stay knowledgeable about release and support lifecycle dates plus associated policies. Reminder: When a platform release reaches End of Support, CA Technologies support of the platform simultaneously reaches End of Support.

Help shape products

CA Technologies invites you to provide input about your CA products and help shape future functionality by participating in the Design Partner Program. To join, email [email protected]

Still have questions or need assistance?

Get answers to your questions and obtain expert help by contacting CA:

  • CA Support
    Get product assistance from CA Support through an online request form, online chat, or by phone. Call CA Customer Care at +1-800-225-5224 in North America or see “Contact Numbers by Region” at Contact CA Support for the local number in your country.
  • CA Services
    Leverage CA expertise for help implementing this release.

Thank you,

CA Technologies Continuous Delivery DirectorTeam