Multi job review app

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Description

Customer would like to trigger or reuse a build, release, deploy job from a review app job

Proposal

As described by customer:

I have a review app job but it has to build, release, and deploy. Can I trigger the build and release jobs or depend on them from my review deploy job?​

A review app requires two jobs: provisioning a version and provisioning a environment . Each job uses the same template, but different job vars.

I could have a review app template and then a prod template .... and maybe combinations of each that are both env and ver and then separate ones for env and ver... but gesh, that would not be near as slick as just having the review app trigger both jobs.

Links / references

Customer issue:

ZD: https://gitlab.zendesk.com/agent/tickets/79616

Customer's current .gitlab-ci.yml can be found within the Zendesk issue.

Documentation blurb

Overview

What is it?

  • Allows a single job to execute multiple stages (build, release, deploy)

Why should someone use this feature?

  • In this case, the customer would like to use a single template to build, release, deploy their app for both their review and production environments.

What is the underlying (business) problem?

  • Better, easier to read code with less duplication

How do you use this feature?

  • Allow jobs to be triggered from within jobs

Use cases

Who is this for? Provide one or more use cases.

GitLab CI/CD customers

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

Edited by 🤖 GitLab Bot 🤖