Ticket #2328 (closed defect: fixed)
Error in Triggerable scheduler when codebase is empty.
| Reported by: | verm | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | 0.8.7 |
| Version: | master | Keywords: | multirepo |
| Cc: |
Description
I hit this error when using the Triggerable scheduler in master:
if not ss_repository: config.error("The codebases argument is not set but still receiving " + "non empty codebase values")
The setup I'm using is rather simple:
- Download source using RCS.
- Create tarball
- Upload tarball to master
- Trigger builders (updateSourceStamp=True)
- ERROR
- Download tarball
- ...
codebases is not set, all source arrives from the same repository.
If I comment this check everything works as expected.
Change History
comment:1 Changed 11 months ago by dustin
- Keywords multirepo added; trigger, scheduler, codebase removed
- Priority changed from major to blocker
- Milestone changed from undecided to 0.8.7
comment:2 Changed 11 months ago by dustin
Ugh, and I get a different error (before the code ever gets to your error) when forcing a triggering build:
File "/Users/dustin/code/buildbot/t/buildbot/master/buildbot/steps/trigger.py", line 155, in start
ss_for_trigger = self.prepareSourcestampListForTrigger()
File "/Users/dustin/code/buildbot/t/buildbot/master/buildbot/steps/trigger.py", line 128, in prepareSourcestampListForTrigger
if codebase in got:
comment:3 Changed 11 months ago by dustin
OK, when I do replicate the error, I get ss = {'codebase': , 'project': , 'branch': u, 'repository': , 'hasPatch': False, 'changes': [], 'revision': u}
comment:4 Changed 11 months ago by dustin
OK, I think that error is 100% bogus. It may, in fact, be the contrapositive of what was intended. But I'll just delete it.
comment:5 Changed 11 months ago by Dustin J. Mitchell
Don't fail triggering if there's no got_revision.
Refs #2328.
Changeset: d7bc842c63372cb455a2914329b9210fd000b148
comment:6 Changed 11 months ago by Dustin J. Mitchell
- Status changed from new to closed
- Resolution set to fixed
Remove bogus check
At the very least, the check's condition is wrong. I think that the text is wrong, and the comment is confusing, too.
Fixes #2328.
Changeset: c84a4e908248cc98353c87470af113a42097a27b
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)