[llvm-dev] Zorg migration to GitHub/monorepo
Galina Kistanova via llvm-dev
llvm-dev at lists.llvm.org
Fri Oct 18 00:05:07 PDT 2019
Hello build bot owners!
The staging master is ready. Please feel free to use it to make sure your
bots would work well with the monorepo and github.
The following builders could be configured to build monorepo:
These builders are already on the staging master. So, please ping me if you
would like to configure any of them to work with monorepo:
These builders have been already tested and could be reconfigured without
staging as soon as public master is ready:
Thanks for your patience and help!
On Thu, Oct 17, 2019 at 5:04 PM Galina Kistanova <gkistanova at gmail.com>
> Hello everyone,
> The build bot is almost ready to move to github.
> As the next step we would migrate the staging master to listen for the
> both changes, from SVN as it was before, and from github.
> Tonight I am going to update the staging (aka silent) master and it will
> start working with github.
> I will send an email when it is done.
> If you bots use one of the ported build factories from the list in my
> previous e-mail, please feel free to stage them for working with
> monorepo/github and once you are happy, let me know, and I'll configure
> them accordingly on the production master. Once that's done, you could move
> the bots back to the production master and you are done.
> When you stage your bot, please follow these steps:
> 1. Stop your bot between builds, if possible,
> 2. Remove the bot working directory (usually this directory has a builder
> name and is under directory where your bot is installed; if you are not
> sure, check the 'builddir' param of your bot in
> 3. Edit buildbot.tac in the directory where your bot is installed. Change
> "port = 9990" line to "port = 9994". Save the change.
> 4. Start your bot, make sure it connects to the staging master.
> 5. Send me a mail with the staged bot names.
> Once you are happy with your bot building monorepo changes from github,
> please send me an e-mail and I'll respond with the instructions of how to
> get your bot back to production.
> Please be aware that staging master could restart often. Please let me
> know if you are having long running builds.
> Feel free to ask if you have questions.
> Please me know if you will see issues with the staging master.
> On Mon, Oct 14, 2019 at 6:16 PM Galina Kistanova <gkistanova at gmail.com>
>> Hello everyone,
>> We are in the middle of porting the majority of zorg to
>> GitHub/monorepo. The following build factories will be ported and if you
>> use one of those for your bots, you are all covered:
>> * ClangBuilder.getClangCMakeBuildFactory (31 bots)
>> * ClangBuilder.getClangCMakeGCSBuildFactory (2 bots)
>> * LibcxxAndAbiBuilder (23 bots)
>> * SphinxDocsBuilder (7 bots)
>> * UnifiedTreeBuilder (11 bots)
>> * ABITestsuitBuilder (1 bot) - based on UnifiedTreeBuilder
>> * ClangLTOBuilder (2 bots) - based on UnifiedTreeBuilder
>> * LLDPerformanceTesuiteBuilder (1 bot) - based on UnifiedTreeBuilder
>> Some build factories will be deprecated. If you use one of these, please
>> change your bot to use something else instead. Here is the list of
>> deprecated build factories:
>> * ClangBuilder.getClangBuildFactory (0 bots)
>> * LLDBuilder (0 bots)
>> * ClangAndLLDBuilder (0 bots)
>> However, some special build factories and build factories with a few bots
>> would need your attention.
>> Here is the list of build factories in need of porting. Patches are
>> * LLVMBuilder (3 bots)
>> * PollyBuilder (3 bots)
>> * LLDBBuilder (6 bots)
>> * SanitizerBuilder (10 bots)
>> * CUDATestsuiteBuilder (1 bot) - depends on
>> * AOSPBuilder (1 bot) - depends on PollyBuilder
>> * AnnotatedBuilder (2 bots)
>> * OpenMPBuilder (2 bots)
>> * FuchsiaBuilder (1 bot)
>> Please feel free to ask if you have questions.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev