On Tue, 5 Jan 2021 at 21:25, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote:
> Hi Jeff, > > > On 1/5/21 10:54 AM, Rainer Orth wrote: > >> > >> I fear I'm a bit lost here myself. I do have a little experience > >> running various builders: > >> > >> * I inherited a Golang one on Solaris/amd64 (based on their own builder > >> infrastructure). > >> > >> * I do run builders for GDB (mostly dormant since Sergio left RedHat) > >> and LLVM on Solaris/amd64 and sparcv9 (both using buildbot). > >> > >> In all three cases the projects provide documentation how to configure > >> your own builders and add them to the infrastructure. Is something like > >> this possible for the GCC Jenkins (say adding Solaris builders) and if > >> so how? Or would one need to setup one's own instance, in which case it > >> would be extremely helpful to learn the necessary config: doing > >> something like this from scratch is a major effort, as seen in Paul > >> Matos' effort (also buildbot-based) of a couple of years ago. > > We don't have any procedures in place for this (yet). I'd like to add > > them, but I'm swamped. > > understood. Often it's easier for an outsider to document a procedure > since he's certain to stumble across every possible roadblock someone > familiar with the system has long forgotten about. > Many roadblocks/barriers, and the complaining newcomers(outsiders) are many times even attacked by the regulars, kind of "it's just opening bash, do this, that, then that that that, pick this, ready". @steering committee Consider transforming the gcc-jenkins to be an open-project (repository, usually patch-update-processes) > > I'm certainly open to having others contribute here. As a long standing > > member of the community I'd be happy to set up an account for you so you > > could wire in a sparc/solaris system executor and set up the build > scripts. > Do I need an account to look at how things work there? I am unable to find even one script from the jenkins UI. Any direct link? > That would be nice. Although my current manual daily regtests do help > and a considerable part of the work is investigating and reporting > failures found, any automatism takes part of the legwork. > > Rainer > > -- > > ----------------------------------------------------------------------------- > Rainer Orth, Center for Biotechnology, Bielefeld University >
