These are the new features, enhancements, resolved issues, and deprecations for the Continuous Delivery for Puppet Enterprise 2.x release series.

Version 2.16.0

Released 19 August 2019

New in this release:
  • Pipeline events summary on the control repo deployment details page. To make it easier for deployment approvers to review the validation events performed on a proposed change, the new What's happened in the pipeline so far? section summarizes the successes and failures in each completed pipeline stage and includes the option to view further details.
  • Impact analysis reports include node names. Impact analysis reports now show the names of the nodes impacted by a proposed change.
Resolved in this release:
  • During the creation of LDAP group mappings, RBAC groups were not listed for renamed workspaces.
  • The Set up Continuous Delivery for PE banner did not show that source control had been integrated after a Bitbucket Cloud instance was added to Continuous Delivery for PE.
  • An inaccurate message about missing PE credentials was shown when you tried to add impact analysis to a pipeline before creating a deployment.
  • In some cases, webhook auto-creation failed for Bitbucket Server.

Version 2.15.1

Released 6 August 2019

Resolved in this release:
  • Deployments from Bitbucket Cloud failed for target branches that did not exist because Continuous Delivery for PE did not automatically create a target branch in these cases.

Version 2.15.0

Released 5 August 2019

New in this release:
  • Bitbucket Cloud support. See Integrate with Bitbucket Cloud for instructions on how to create an OAuth application to start using your organization's Bitbucket Cloud repositories with Continuous Delivery for PE.
  • Delete workspaces. A workspace's owner can now delete the workspace by visiting the Workspace tab in Settings. Super users can also delete workspaces.
Resolved in this release:
  • The full Continuous Delivery agent version number was not shown on the Job Hardware page or returned when you ran distelli agent version.
  • Blank rows appeared in the workspaces menu.
  • When configuring impact analysis after adding PE credentials on the New Deployment screen, a PE credentials with the specified name already exist. error was shown.

Version 2.14.2

Released 29 July 2019

Resolved in this release:
  • The prefixed environment selection option did not appear for users with more than one PE instance integrated with Continuous Delivery for PE.

Version 2.14.1

Released 24 July 2019

Resolved in this release:
  • If your trial or production license expired, you were unable to successfully upload a new license.

Version 2.14.0

Released 22 July 2019

New in this release:
  • Redesigned manual deployment workflow. When you create a new manual deployment for control repos and modules, Continuous Delivery for Puppet Enterprise no longer prompts you to select a branch. The branch for your new deployment now automatically matches the pipeline you've selected. To override this setting, click Edit and select a new branch name.
  • Usability improvements. We've made numerous small usability improvements, including:
    • A larger log window on the Job Details page, allowing you to see more information before you have to scroll.
Resolved in this release:
  • If you had only one PE instance integrated with Continuous Delivery for PE, and that PE instance contained prefixed environments, the prefixed environments did not appear when you created a deployment.
  • Some buttons on the SAML, LDAP, and SSL configuration screens were blank.
  • The option to add impact analysis task to a regex branch pipeline was included erroneously, and has been removed.
  • Super users could not install global shared job hardware.

Version 2.13.4

Released 16 July 2019

Resolved in this release:

  • In automated runs, module deployments to prefixed environments resulted in errors.

Version 2.13.3

Released 16 July 2019

Resolved in this release:
  • Performing a manual module deployment to prefixed environments resulted in errors.

Version 2.13.2

Released 15 July 2019

Resolved in this release:
  • In certain cases, impact analysis incorrectly reported that resources had changed.

Version 2.13.1

Released 12 July 2019

Resolved in this release:
  • If any catalog did not successfully compile during an impact analysis task, the task failed.
  • The presence of certain parameter value types in impact analysis reports caused page crashes.
  • Changes to data types marked sensitive were shown as modified in some impact analysis reports.

Version 2.13.0

Released 11 July 2019

New in this release:
  • Redesigned impact analysis reports. We've updated the format of impact analysis reports to improve usability and provide you with greater detail about how the resources on your nodes will be impacted as a result of code changes.
  • Generate impact analysis reports on demand. You can now generate an impact analysis report for any change by clicking New Impact Analysis on a control repo's details page.
  • Trial mode. When you set up Continuous Delivery for PE for the first time, you now have the option to select Trial Mode, which launches a seven-day trial period without requiring a license. At the end of the trial period, you are prompted to generate and upload a free 30-day trial license.
  • Usability improvements. We've made numerous small usability improvements, including:
    • When logging back into Continuous Delivery for PE, you are automatically returned to the workspace you last used.
    • When an upstream pipeline dependency fails, downstream jobs and deployments are now labeled canceled instead of failed.
    • An improved error message if you create a username that includes non-supported characters.
Resolved in this release:
  • Impact analysis required reconfiguring after you upgraded Puppet Enterprise to version 2019.1.
Removed in this release:
  • Chronological event view. We've removed the option to view a chronological event history for your control repo or module.

Version 2.12.2

Released 21 June 2019

Resolved in this release:
  • If you did not create any groups in your Continuous Delivery for PE user account before upgrading to version 2.12.0 or 2.12.1, you were unable to access the workspace that was automatically created for your user account as part of the upgrade.

Version 2.12.1

Released 19 June 2019

Resolved in this release:
  • If you renamed a workspace and then navigated to a page in the Settings menu, you were redirected your default workspace.
  • User names were listed in the workspaces menu.
  • The link to a newly created workspace in the workspaces menu didn't work properly until the page was refreshed.

Version 2.12.0

Released 17 June 2019

New in this release:
  • Workspaces. Teams using Continuous Delivery for PE need to share common resources, such as control repos, modules, pipelines, and jobs. Workspaces is a redesign of the users and team model in previous versions of Continuous Delivery for PE, and was created to make sharing resources with team members simpler and more intuitive. To learn more about how to set up and use workspaces, see Managing workspaces.
    Note: If you're upgrading to version 2.12.0 from an older version of Continuous Delivery for PE, your existing user accounts have been converted to workspaces.
  • Redesigned navigation. We've updated the navigation bar and moved it to the left side of your screen, bringing Continuous Delivery for PE into better visual and interface alignment with Puppet Enterprise.
  • Global shared hardware. You can now set up global shared job hardware servers that are available to all workspaces in your Continuous Delivery for PE installation. Once global shared job hardware is configured, you can instruct a job to use shared hardware when creating or editing the job. To get started, see Configure global shared job hardware.
  • Link to the root console for super users. Super users will now find a Root Console link in the workspaces menu at the top of the navigation bar.
  • Add all members of an Active Directory or LDAP group to a workspace. You can add existing LDAP or Active Directory groups to your installation's workspaces by clicking Manage Groups in the Single Sign On tab in the root console's Settings area.
  • Support for unauthenticated SMTP. When configuring SMTP, you are no longer required to enter a username and password.
  • Select from available hardware capabilities. When creating a new job, you're now shown a checklist list of available job hardware capabilities. This list is automatically populated by the capabilities you've set on your workspace's job hardware, as well as the capabilities on any available global shared job hardware.
  • Usability improvements. We've made numerous small usability improvements, including:
    • In the Edit Job pane, pressing Enter no longer saves and exits an in-progress job.
    • When you click the link to a commit SHA on a module's deployment details page, the link opens in a new browser tab.
    • Deployments to protected environments now wait until all dependencies are complete before issuing an approval request.
    • You'll see more helpful error messages when an impact analysis task fails.
Resolved in this release:
  • Prefixed environments failed to deploy successfully in certain circumstances.

  • The status of a commit in GitLab was not updated correctly once a pipeline stage completed.
  • In certain cases, impact analysis reports displayed an error when nodes in an environment had the potential to be impacted, but no impact was actually detected.
  • If you added new PE credentials and gave them the same name as existing credentials, the existing credentials were overwritten.
  • Users for whom Continuous Delivery for PE is not connected to the internet and analytics data collection is disabled received Google communication log warnings.

Version 2.11.1

Released 10 June 2019

New in this release:
  • Bitbucket Server webhooks created automatically. Webhooks are now created automatically when you integrate Bitbucket Server (5.x series and newer versions) with Continuous Delivery for PE. You no longer need to manually configure plugins for webhooks or pull requests, as was required with the 4.x series.
Resolved in this release:
  • In some circumstances, PostgreSQL database users' jobs could not exit a pending state.

Removed in this release:
  • Bitbucket Server 4.x series support for new users. The Bitbucket Server 4.x series is no longer supported for new users who are setting up Continuous Delivery for PE for the first time.

Version 2.11.0

Released 28 May 2019

New in this release:
  • Deploy module code from a regex branch pipeline to a feature branch Puppet environment. You can now deploy module code from a regex branch pipeline. When triggered, this deployment uses the Feature Branch deployment policy to deploy the new code to a Puppet environment with the same name as the branch where the new code is housed. If a Puppet environment by this name doesn't exist at the time of deployment, Continuous Delivery for PE creates it for you.

Resolved in this release:
  • You were unable to connect Continuous Delivery for PE to an LDAP server when using an insecure LDAP connection.

Version 2.10.1

Released 20 May 2019

Resolved in this release:

  • Module deployment reports didn't work with disk storage. Disk storage users were not able to create or download module deployment reports.

  • Users could not render the upload-license page. This change fixes a previously unreported issue where a user could not visit the upload license page.

Version 2.10.0

Released 13 May 2019

Important security notice:
  • Select data was collected on accounts that have opted out of data collection. We recently discovered that Continuous Delivery for PE was erroneously collecting select analytics data from accounts that had opted out of analytics data collection. We resolved this issue and have destroyed all analytics data collected on or before 9 May 2019, regardless of whether the data was collected as a result of this issue. To learn more about the data we collect, see Analytics data collection.

New in this release:
  • Module deployment reports. You can now generate a module deployment report that lists the most recent commit SHA in each environment in Continuous Delivery for PE for the 10 most recently deployed modules. The module deployment report is a comma-separated value (CSV) file, and can be downloaded and imported to the tool of your choice. To generate a module deployment report, click the reports icon on theModules page.

  • Usability improvements. We've made numerous small usability improvements, including:
    • All forms can now be submitted by pressing the Enter key.

    • You can now show or hide the value of your Artifactory access token when adding credentials.

    • Success messages are no longer shown in red text in logs.

    • Improved error messaging when an invalid private key is added during impact analysis configuration.

Resolved in this release:
  • When you added a new control repo or module and were prompted to integrate your source control system, the newly added source control system was not selected correctly when you returned to the module or control repo creation screen.

Removed in this release:
  • Job history. We've removed the job history timeline from the Jobs page.

Version 2.9.1

Released 30 April 2019

Resolved in this release:
  • MySQL users were unable to run Continuous Delivery for PE version 2.9.0.

Version 2.9.0

Released 30 April 2019

New in this release:
  • Pipeline stage status shown in your source control system. The status of each stage of the relevant pipeline is now shown alongside a commit or pull request in your source control system.

  • Master branch creation for new modules. When you add a new module to Continuous Delivery for PE, the software now checks to see if the module contains a master branch. If no master branch is present, Continuous Delivery for PE offers to create one for you from an existing branch of your choosing. For more on the master branch and its importance, see Git branches and Continuous Delivery for PE.

  • Name a newly created pipeline stage. To assign a custom name to a newly created pipeline stage, fill in the Name field when adding the new stage.
  • Usability improvements. We've made numerous small usability improvements, including:
    • If an impact analysis task fails, a Failed message is now shown in the pipeline and events views.

    • You can now show or hide the value of your GitHub Enterprise token when adding credentials.

Resolved in this release:
  • Due to a Firefox known issue, Firefox users saw a blank screen when opening a message in the message center.

  • When editing the later stages of a long pipeline, the editing modal often appeared above the visible area of the browser window.

  • Clicking Edit Deployment too soon after a new page load caused an error.

  • A non-descriptive error was shown when you attempted to deploy to a node group that didn't contain any nodes.

  • When adding new PE credentials, relevant fields were not displayed for manual entry of information not automatically discovered by Continuous Delivery for PE.

  • The Edit Impact Analysis screen did not accurately show the environments you chose to run impact analysis tasks on.

Version 2.8.2

Released 25 April 2019

Resolved in this release:

Version 2.8.1

Released 18 April 2019

Important security notice:
  • Root passwords were exposed in the PE console for some users. If you used the cd4pe::root_configuration task to configure your Continuous Delivery for PE installation, the root user's username and password were exposed in the job's Job Details pane in the PE console. To fix this issue, upgrade the puppetlabs-cd4pe module to version 1.2.1 and reset the root user's password.

Version 2.8.0

Released 15 April 2019

Important notice for users upgrading to version 2.8.0:
  • A Continuous Delivery agent upgrade is required on all SELinux-enabled job hardware. This version features improved support for distribution-packaged Docker on hosts with SELinux enabled. Mounting volumes from the host to the Continuous Delivery for PE container now tells SELinux to allow the container access to the volume mount. If you have SELinux enabled, you must upgrade your Continuous Delivery agents. For instructions, see Upgrade the Continuous Delivery agent.

New in this release:
  • View a control repo or module's event history sorted by pipeline run. You can now choose to view the event history for your control repo or module by pipeline run, rather than by chronological event. To get started, choose View history by: Pipeline on your control repo or module's Events pane.
    Note: If you're upgrading to Continuous Delivery for PE version 2.8.0, please note that we are unable to retroactively sort your event history from previous versions of the software into pipeline runs. Only pipeline runs triggered using version 2.8.0 and newer versions are shown in the pipeline view.
  • Automatic Git branch creation when deploying a module to an environment without a matching branch. When you deploy a module to an environment for which a matching Git branch does not yet exist, Continuous Delivery for PE now creates the branch for you.

  • Set a deployment's timeout duration. When creating a new deployment, you can now specify the length of the deployment's timeout period. By default, deployments time out after 60 minutes.

  • Name your pipeline stages. You can now provide custom names for the stages in your control repo and module pipelines. To name or rename a pipeline stage, click the More Actions menu and selectRename Stage.

  • Support for custom CA certificates for GitHub Enterprise. When setting up your GitHub Enterprise integration, you now have the option to provide a custom CA certificate, such as a self-signed certificate.

  • Usability improvements. We've made numerous small usability improvements, including:
    • The description you provide for a manually triggered module deployment is now shown in the module's events timeline and on the deployment's details page.

Resolved in this release:
  • If you enabled SAML and then ran a configuration test, SAML was disabled until you re-saved the integration.

  • A display error occurred if you reordered the stages of a default pipeline while the pipeline contained stage placeholders.

  • When using GitHub Enterprise with self-signed certificates, an error was shown when you ran a job.

Removed in this release:
  • Dispatch a job. We've removed the ability to manually dispatch a job from the Jobs page.

Version 2.7.1

Released 2 April 2019

Resolved in this release:
  • When manually triggering a regex branch pipeline for a control repo, the branch selection section of the Run Pipeline page was unresponsive.

Version 2.7.0

Released 1 April 2019

New in this release:
  • Default pipelines. When creating a new pipeline for a control repo or module, Continuous Delivery for PE now offers to set up a default pipeline for you. Default pipelines contain recommended stages along with prompts to build out the pipeline's functionality. You can edit and rearrange the elements of the default pipeline to suit your needs. To get started, click + Add default pipeline when creating a new pipeline.

  • SSL support. To learn how to set up SSL for your Continuous Delivery for PE instance, see Configure SSL.

  • Notification of upcoming token expiration. You'll receive a notification in the message center when yourPE token is two weeks from its expiration date, and another notification if the token expires.

  • Updated guidance and new default queries for setting up regex branch pipelines. These changes are designed to help you avoid accidentally triggering the regex branch pipeline when changes are deployed to your environment branches.

  • Usability improvements. We've made numerous small usability improvements, including:
    • You are no longer required to generate and enter a new PE token when adding or editing impact analysis credentials after integrating your PE instance.

    • Improved messaging when configuring storage in the root console.

Deprecated in this release:
  • Incremental branch and blue-green branch deployment policies. The incremental branch and blue-green branch deployment policies have been deprecated. These deployment policies will be removed from Continuous Delivery for PE in a future release.

  • Support for Puppet Enterprise version 2017.3. PE 2017.3 has reached the end of its support lifecycle.

Version 2.6.0

Released 18 March 2019

New in this release:
  • Module deployments. You can now deploy module changes to your Puppet environments using your module's pipeline. In order to deploy module code, you must first add a :branch => :control_branch declaration to the module's section of your Puppetfile. See Deploy module code for more information.

  • Master branch creation for new control repos. When you add a new control repo to Continuous Delivery for PE, the software now checks to see if the control repo contains a master branch. If no master branch is present, Continuous Delivery for PE offers to create one for you from an existing branch of your choosing. For more on the master branch and its importance, see Git branches and Continuous Delivery for PE.

  • No-op runs for deployments. When creating a new deployment for a control repo, you now have the option to set the deployment to run in no-op mode. No-op deployments are not available for regex pipelines or deployments using the eventual consistency deployment policy.

  • Redesigned Puppet Enterprise account settings page. The Puppet Enterprise account settings page now displays each connected PE instance's node classifier address, number of protected environments, and token expiration date.

  • Specify the lifetime of your PE token. When adding new PE credentials using basic authorization, you can now customize the lifetime of the PE token Continuous Delivery for PE generates for you.

  • Regenerate a PE token. On the Puppet Enterprise account settings page, click Regenerate to enter a new API token or provide your PE credentials to have a new token generated for you.

  • Run job hardware on Ubuntu 18.04. You can now install the Continuous Delivery agent on systems running Ubuntu 18.04.

  • Usability improvements. We've made numerous small usability improvements, including:
    • Improved messaging when setting up a deployment using the feature branch policy.

    • No longer requiring a deployment description when adding a deployment to a pipeline stage,

    • Reorganized the steps for creating a new deployment for a more logical flow.

Resolved in this release:
  • All deployments with stagger settings ran batches of 10 nodes at a time, rather than the number of nodes specified when the deployment was created.

  • The Update Ref section of the deployment details page was not displayed for deployments using the eventual consistency deployment policy.

  • Terminate conditions were not shown on the deployment details page for deployments using the direct merge deployment policy.

Version 2.5.0

Released 4 March 2019

New in this release:
  • Deploy code from a regex branch pipeline to a feature branch Puppet environment. You can now add a deployment to your regex branch pipeline. When triggered, this deployment uses the Feature Branch deployment policy to deploy the new code to a Puppet environment with the same name as the branch where the new code is housed. If a Puppet environment by this name doesn't exist at the time of deployment, Continuous Delivery for PE creates it for you.

  • Manually trigger a regex branch pipeline. You can now start a pipeline run on a regex branch pipeline by clicking Run Pipeline .

  • Onboarding guide for first-time users. New users are now greeted by a guided path through the integrations and setup tasks required to get started with Continuous Delivery for PE.

  • Reorder pipeline stages. You can now change the order in which the stages in your pipeline appear. Click the More Actions menu and selectReorder Stages.

  • Support for pull requests from forked repositories. The Continuous Delivery for PE pull request (PR) gate workflow now accepts PRs from forked repositories in GitHub, GitLab, and Azure DevOps. Pull requests from forked repositories on Bitbucket Server are not currently supported.

Resolved in this release:
  • The New LDAP Configuration screen's close control was not operational.
Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.