Allow environment stop jobs to be defined in downstream pipelines

Problem to solve

Based on discussion in #389068 (closed).

When using downstream pipelines for deployments, currently any on_stop actions must be defined in the parent pipeline or they will not be executed when the environment is stopped.

Proposal

When searching for potential stop actions for an environment, also consider any downstream pipelines belonging to the latest successful deployment (parent) pipeline.

Links

• https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html#downstream-pipelines-for-deployments
• https://docs.gitlab.com/ee/ci/environments/#multiple-stop-actions-for-an-environment

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.