RE: [isar-cip-core][PATCH v4 0/3] Enable Debian Sid support
| Newsgroups | org.cip-project.lists.cip-dev |
|---|---|
| Message-ID | <TYWPR01MB110635B2601B887DFEF2DCB27C7ED2@TYWPR01MB11063.jpnprd01.prod.outlook.com> |
Hi Jan, > it is a protected one, and that likely prevented that you could define this. Right, it makes sense. Thank you, I confirmed the new scheduled pipeline is created for "next" branch. Thanks & Regards Shivanand K -----Original Message----- From: Jan Kiszka <[email protected]> Sent: 24 June 2026 01:46 To: kunijadar shivanand(TSIP DITC_DIT-OST) <[email protected]>; [email protected] Cc: balakumar adithya(TSIP DITC_DIT-OST) <[email protected]>; dinesh kumar(TSIP DITC_DIT-OST) <[email protected]>; hayashi kazuhiro(林 和宏 □DITC○CPT) <[email protected]> Subject: Re: [isar-cip-core][PATCH v4 0/3] Enable Debian Sid support On 23.06.26 15:01, [email protected] wrote: > Hi Jan, > > Thank you for the minor changes. > > I have one request, the scheduled pipeline "Weekly Debian Sid build & tests" here https://gitlab.com/cip-project/cip-core/isar-cip-core/-/pipeline_schedules was used for testing, but I'm unable to change the branch to "next" due to the below error. > > "The current user is not authorized to update the pipeline schedule" > > Could you please create new scheduled pipeline using "next" branch with same options (if interval & time zone are fine)? > Make sure to define CI variable "CI_RUN_UNSTABLE_SID" in this pipeline. > I've taken ownership of your schedule and was able to point it to the next branch - it is a protected one, and that likely prevented that you could define this Jan -- Siemens AG, Foundational Technologies Linux Expert Center