Separate gocd/botmaster instance for SLES
Hello openSUSE! This is a heads, opensuse infrastructure remain unaffected. We will keep maintaing gocd pipeline configuration in openSUSE-release-tools. SLES will move their botmaster *gocd pipelines from botmaster.suse.de, which was previously used by both openSUSE and SLES, to a separate host. This is due to meet SALSA requirements for SLES 15.5. SLES Release Management seems to be demanding support from the autobuild team, including a 4-eyes review of changes to botmaster pipelines, etc. Multiple people (bcc'ed) outside the autobuild team have root access to the botmaster.suse.de, which is why the autobuild team plans to have a brand new botmaster/gocd instance built from scratch. SLES also mentioend plans to perhaps separate SLES gocd pipeline configuration (not the pipeline code etc) from openSUSE-release-tools into a separate package. In this way, people who previously had root access to botmaster.suse.de can keep the access and continue working as before. [0] https://github.com/openSUSE/openSUSE-release-tools [1] https://www.gocd.org/ Best regards Lubos Kocman
Hi, On Fri, Jul 08, 2022 at 01:53:21PM +0000, Lubos Kocman wrote:
Hello openSUSE!
This is a heads, opensuse infrastructure remain unaffected. We will keep maintaing gocd pipeline configuration in openSUSE-release-tools.
SLES will move their botmaster *gocd pipelines from botmaster.suse.de, which was previously used by both openSUSE and SLES, to a separate host.
This is due to meet SALSA requirements for SLES 15.5. SLES Release Management seems to be demanding support from the autobuild team, including a 4-eyes review of changes to botmaster pipelines, etc.
Just to be correct, this is "SLSA" from https://slsa.dev/ , a guideline and standardization effort to supply chain hardening of buildsystems and processes. Ciao, Marcus
participants (2)
-
Lubos Kocman
-
Marcus Meissner