Hi Jeff,

> On 1/5/21 10:09 AM, abebeos wrote:
>>
>>
>> On Tue, 5 Jan 2021 at 18:50, Jeff Law <l...@redhat.com
>> <mailto:l...@redhat.com>> wrote:
>>
>>
>>
>>     On 1/5/21 2:18 AM, abebeos wrote:
>>     >
>>     > On Mon, 4 Jan 2021 at 21:40, Jeff Law <l...@redhat.com
>>     <mailto:l...@redhat.com>
>>     > <mailto:l...@redhat.com <mailto:l...@redhat.com>>> wrote:
>>     >
>>     >     On 12/31/20 7:13 AM, abebeos wrote:
>>     >     [...]
>>     >     >     >         I'm definitely curious about the testing
>>     setup and
>>     >     >     whether or
>>     >     >     >         not it can
>>     >     >     >         be replicated into our Jenkins setup. 
>>     >     >     >
>>     >     >     >
>>     >     >     >     Where can I find this Jenkins setup?
>>     >     >     >
>>     >     >     >
>>     >     >     > To close this: assuming " into our Jenkins setup" is
>>     some
>>     >     redhat
>>     >     >     > internal jenkins setup.
>>     >     >     No, it's public.
>>     >     >
>>     >     >     http://gcc.gnu.org/jenkins
>>     <http://gcc.gnu.org/jenkins> <http://gcc.gnu.org/jenkins
>>     <http://gcc.gnu.org/jenkins>>
>>     >     <http://gcc.gnu.org/jenkins <http://gcc.gnu.org/jenkins>
>>     <http://gcc.gnu.org/jenkins <http://gcc.gnu.org/jenkins>>>
>>     >     >
>>     >     >
>>     >     > (sidenote: This resolves on my side to the (insecure)
>>     >     > http://3.14.90.209:8080/ <http://3.14.90.209:8080/>
>>     <http://3.14.90.209:8080/ <http://3.14.90.209:8080/>>
>>     >     <http://3.14.90.209:8080/ <http://3.14.90.209:8080/>
>>     <http://3.14.90.209:8080/ <http://3.14.90.209:8080/>>>)
>>     >     Yup.
>>     >
>>     >     >
>>     >     > Is the source-code of  http://gcc.gnu.org/jenkins
>>     <http://gcc.gnu.org/jenkins>
>>     >     <http://gcc.gnu.org/jenkins <http://gcc.gnu.org/jenkins>>
>>     >     > <http://gcc.gnu.org/jenkins <http://gcc.gnu.org/jenkins>
>>     <http://gcc.gnu.org/jenkins <http://gcc.gnu.org/jenkins>>>
>>     >     available somewhere? I could not locate it.
>>     >     Jenkins is a project independent of GCC for building continuous
>>     >     testing/delivery systems.  See http://jenkins.io
>>     <http://jenkins.io> <http://jenkins.io <http://jenkins.io>>
>>     >
>>     >
>>     > Oh, my bad - I was referring to the sources of gcc's project jenkins
>>     > setup (the scripts, configs etc. for the different targets,
>>     including
>>     > avr).
>>     The Generators subdirectory has jobs which are used to rebuild the
>>     various target jobs.  They're broadly categorized by the type of
>>     build. 
>>     ie, pure native, qemu-emulated native, glibc cross, newlib cross
>>     and no
>>     runtime library.  avr IIRC fits into the final category as it doesn't
>>     have an upstreamed glibc or newlib port.
>>
>>
>> Ok, but I'm still unable to find the sources ("Generators
>> subdirectory"?). Can you (or anyone else) give me a direct link to the
>> sources? E.g. I want to change the avr part, where do I start
>> (usually, a git repo.)?
> You're not going to be able to change the scripts.   BUt they are
> accessable from the web site.  They're not in GIT or anything like that.

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.

Thanks.
        Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

Reply via email to