Epic Goal

• Template for creating a new component should allow users to select Azure Pipelines as a CI provider

Why is this important?

• Provide more CI options to the user for which customer may not necessary to be using Tekton only CI

Scenarios

1. Add option to existing templates to use Azure pipeline (sample Azure pipeline resource: https://github.com/lcarva/azure-pipelines-java/blob/main/azure-pipelines.yml)
2. Generate repo with Azure pipeline resources
3. Identify Azure plugin requirement, e.g. annotation, permissions, for the pipeline to show in RHDH, etc., and feed those requirements to the build and install team to make the changes on the CI resources and the installer

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• A new branch to be created under the https://github.com/redhat-appstudio/tssc-sample-templates repo to host the AI software template

Dependencies (internal and external)

1. Build tasks and required Azure CI resources are provided by the Build team
2. Installer provide the required resources to run the Azure pipeline
3. Installer need to setup the plugin with authentication before we can test out the feature

Previous Work (Optional):

1. …

Open questions::

1. Need to get information from the build team on the exact Azure pipeline resources and how the directory structures on how the created application resources will look like in the created application repo

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment