[lldb-dev] buildbot deployment: gsutil: Anonymous caller does not have storage.objects.create access to lldb_test_traces

[Pavel Labath via lldb-dev]

On Thu, 2 Aug 2018 at 13:39, Jan Kratochvil <jan.kratochvil at redhat.com> wrote:
>
> On Thu, 02 Aug 2018 13:47:25 +0200, Pavel Labath wrote:
> > However, I strongly suspect that you do not want this,
>
> Right.
>
>
> > *However*, for setting up a new bot, I'd recommend not using this
> > particular slave factory (getLLDBScriptCommandsFactory) at all,
> > because it's heavily customized for our use case (*), and very
> > different from how typical llvm buildbots are set up. You might be
> > better off setting up a new factory, which just does the typical
> > checkout+build+(optional) test steps, and avoids all of this mess.
>
> OK. For development of these new steps I guess I should run my own buildbot
> master instance? As otherwise that will be probably several/many commits to
> zorg repo (+requested buildbot master restarts) and I may screw up something
> along.

Yes, that would definitely be the best, but last time I tried that, I
couldn't get my master instance to run, for any approximation of the
word "run" (which is part of the reason why I haven't done anything
about this slave factory, even though I really don't like it)..