tardyp changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.2.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
<tardyp> uovobw: you should probably post a github issue/discussion for this lengthy question
<tardyp> it looks like you are missing default configuration for codebase so that repo1 can pickup the default branch
<uovobw> tardyp: possibly, yes, thanks for the idea. what i was actually missing was understanding the vision of builbot, so i was passing branches and repos around the config instead of using the util.Property() values that were auotmatically being set. it's now working as intended, i just had to Learn To Stop Worrying And Trust The Tool
vmeson has joined #buildbot
<tgamblin> Hello, I'm trying to get a RemoteStartCommand object running as part of a build pipeline, and I'm running into this error when calling start(): builtins.AttributeError: 'RemoteShellCommand' object has no attribute 'start'
<tgamblin> But I understand from the documentation that RemoteShellCommand should inherit that function from RemoteCommand - is that still correct?
Zash has joined #buildbot
<tgamblin> Ah, it's been changed to _start
<tardyp> if it is _something, it means its private.
<tardyp> you shouldn't be using those class
<tgamblin> tardyp: Thanks, I think I have my mistakes figured out. Was trying to get fancy with RemoteShellCommand for a canStartBuild implementation, but I think the example in the docs was the right thing to follow in the first place
bdbaddog has joined #buildbot
<tardyp> doc is always right until it isn't :)