v3.0.11

Bug Fixes

• Fixed detection of Perl-based hooks. This was broken when Perl-based addon hook support was added.

Pipeline Improvements and Bug Fixes

• These were ported forward from 2.8.13 to resolve some issues with the Genesis deployment pipelines:

  • The pipelines have removed support for hipchat and stride messaging, but since these services have been shut down by their provider (Atlassian) ages ago, no one should still be using them

  • Switched the default pipeline task image to genesiscommunity/concourse from starkandwayne/concourse. This is to reflect the new location of the official Concourse task image.

  • The pipeline now has a new key, require-passed-caches, which is a boolean value. If true, the pipeline will require that the previous environment successfully deployed before deploying the next environment (the classic and currently default behavior).

    If set to false, the pipeline will be loosely coupled to the previous environment deployment, relying on the updates it does to the cache in the git resource to trigger the next environment. This will become the default behavior in the future, but for now it is opt-in.

    The reason for this change is because previously the pipeline would push versions to the passed cache resource that would not actually satisfy the file path updates that it filters on, meaning that if the configuration of the resource changes, the versions would not be detected as a passed resource, and the pipeline would not allow the next environment to deploy.

  • Fixes the generation of the cache resource in the pipeline definition. The previous implementation was using the input to the bosh-deploy task, but that wasn't available in the generate-cache task, but instead got the previous cache passed in as the 'out' input (confusing, I know).

  • This also triggers a check of the cache resources for each following environment, so changes pushed to git that match the file filters on the caches will be immediately available to the next environment, rather than waiting for the resource check period to expire.

  • Added version_depth to git resource in ci.yml. This allows for retrieving more than one commit from the git repository. This is important in the case where the git resource gets reset due to its configuration changing, such as rotating credentials, and the pipeline losing references to commits that last passed the various bosh-deployment jobs.