Add a quick link to create issue from the scheduled pipeline report (!6041) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Proposal to add a quick link to create issue on the scheduled pipeline report, this will be displayed just under the existing 🕵️ notes link as:

🐞 Create Issue

it's only displayed for the run of the day (if the status is not a success), the link is formatted to create a pre-filled issue that looks like this:

:warning: Scheduled Pipeline Report Issue

<!--
**Please remember to click the "Keep" button for job artifacts before submitting this issue!**
**Also specify the version/branch where the issue occurred**
-->

The scheduled pipeline run for **☁capo 🚀rke2 🎬nightly 🛠ha 🐧suse** on 2025-11-12 has failed.

**Report Details**
- [**Report Link**](https://gitlab.com/sylva-projects/sylva-core/-/wikis/Scheduled-pipelines-report/2025-11-12)
- [**Failed Pipeline**](https://gitlab.com/sylva-projects/sylva-core/-/pipelines/2153418497)

**Failing Jobs & Status**

- **Overall Status:** 🔴 Deployment/upgrade Failed
- **Failing Jobs:**
- [deploy-workload-cluster](https://gitlab.com/sylva-projects/sylva-core/-/jobs/12055140179) (failed)

/labels ~CI-breakage, ~type::bug

*This issue was auto-generated from the scheduled pipeline report. Please add any relevant notes below.*

It contain an "invisible" header section to remind to the CI analyst who create the issue to not forget to click on keep artifact button, to mention branch/version related to the pipeline (as this info is not easy to extract)

Then we could find the pipeline name, date, direct link to the dated report and failed pipeline and the detail of failed job

The issue is then auto labeled with CI-breakage & typebug

Related reference(s)

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Add a quick link to create issue from the scheduled pipeline report

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports