Skip to content

VSD Scheduled Reports - convert to a CI/CD component

Overview

We have an opportunity for a cross-stage collaboration between groupoptimize and grouppipeline authoring. The suggestion is to create a component that generates that artifact, and later on we could add that component to the CI/CD catalog.

This will solve the problem we have today with templates (you can read about them on this section in the direction page) and we can benefit by dogfooding components and catalog.

Proposal

Once grouppipeline authoring will finished the restructuring the CI components - groupoptimize convert the Delivery Setting - pipeline template to a component that will take an artifact from the report generation pipeline and open an new issue.

Related to this comment, and Customer feedback from the VSD Post-release survey.

Implementation plan

  1. Move the latest code to the public repo.
  2. Set up the CI/CD catalog specific YAML file.
  3. Set up a test project where we try invoking/scheduling the the CI job which invokes the catalog code.
  4. Documentation? (may be a follow-up)

CI/CD catalog component requires a publicly accessible repository thus we need to move the latest code.

Edited by Haim Snir