verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: | tutorial: | irclogs:
troglodito has quit [Ping timeout: 248 seconds]
troglodito has joined #buildbot
troglodito has quit [Ping timeout: 240 seconds]
troglodito has joined #buildbot
_whitelogger has joined #buildbot
mark_ is now known as mjw
vext01 has joined #buildbot
<vext01> hi
<vext01> tried to add some nightly builds to our buildbot instance
<vext01> using this fragment:
<vext01> it ran builds, but for random repos...
<vext01> any idea why?
<vext01> one theory is that its cloning the last repo that it ran a build for, ignoring the url in the codebases argument
<vext01> seems to be to do with createAbsoluteSourceStamps=True
<vext01> killing that seems to make it work
<sknebel> TheOnlyJoey: I think the schedulers config for the repos would be relevant to your issue
<cmouse> fg
<cmouse> whups
<Zash> cmouse, it's dangerous to go alone, take this: ^Z
<cmouse> =)
TheOnlyJoey has quit [Quit: Client closed]
dol-sen has quit [Remote host closed the connection]
TheOnlyJoey has joined #buildbot
<TheOnlyJoey> ugh got disconnected
<TheOnlyJoey> sknebel: Using a SingleBranchSecheduler in this case
<TheOnlyJoey> I kind of assumed the problem was in the GitPoller though, since a force build did compile without forcing index
<TheOnlyJoey> As it only does the 'git checkout' step on the gitpoller's builds (without it just git pull's and does not care)
mjw has quit [Killed (NickServ (GHOST command used by mark_!]
mark_ has joined #buildbot
<glogan> Is there a way to up the column lengths in the DB?
<glogan> I'm seeing stuff like buildbot.config.errors.ConfigErrors: Step ShellCommand name 'Ensure ingest script requirements are present in env' exceeds maximum length of 50 more than I'd like
troglodito has quit [Ping timeout: 240 seconds]
troglodito has joined #buildbot