Opened 3 years ago

Closed 3 years ago

#3416 closed defect (fixed)

Force scheduler example is not compatible with nine

Reported by: dustin Owned by: dustin
Priority: major Milestone: 0.9.+
Version: master Keywords:
Cc:

Description

From https://github.com/buildbot/buildbot/commit/6f497b4d8e3f4ab2f2bb8bbb6e5c21f92e6784b4#commitcomment-15547418 regarding the example for the ForceScheduler in https://github.com/buildbot/buildbot/blob/master/master/docs/manual/cfg-schedulers.rst

---

This example is not working with v0.9 anymore as branch, revision, etc parameters are removed. I'm trying to figure out what is the correct way of customizing Force Scheduler form in Buildbot 0.9 and how to specify branch to be built.

If someone could provide a hint for the correct syntax, I'd be happy to contribute the update to documentation. Thanks!

Change History (7)

comment:1 follow-up: Changed 3 years ago by dustin

Are these parameters in the codebase now?

comment:2 in reply to: ↑ 1 Changed 3 years ago by zoresvit

Replying to dustin:

Are these parameters in the codebase now?

As far as I understand the docs and code, yes, branches are now specified as part of codebases parameter. However I couldn't figure out how to use it properly.

Overall I want to figure out 2 things with Buildbot 0.9:

  1. How to specify branches to ForceScheduler? via codebases?
  2. How to create web form to ask user for specific branch in the web UI?

Thanks!

comment:3 follow-up: Changed 3 years ago by pedersen

for buildbot9 beta 5 the following worked ..

c['schedulers'].append(schedulers.ForceScheduler(
    name="Release", # (will bump build number, upload installers and run tests)
    builderNames=["ReleaseBuilder"],
    reason=util.StringParameter(name="reason",label="Reason:", required=True, size=80),
    username=util.UserNameParameter(label="Who are you:", size=80),
    codebases = [ util.CodebaseParameter(
        "",                         # need to pass a value ("")
        name = "Main repository",
        branch=util.ChoiceStringParameter(
            name="branch",
            choices=["master", "hest", primaryBranch],
            default="master"),
            
            # will generate nothing in the form, but revision, repository,
            # and project are needed by buildbot selfcheduling system so we
        revision=util.FixedParameter(name="revision", default=""),
        repository=util.FixedParameter(name="repository", default=""),
        project=util.FixedParameter(name="project", default=""),
        ) ],
        
    properties = [],
    ))
Last edited 3 years ago by pedersen (previous) (diff)

comment:4 Changed 3 years ago by dustin

  • Owner set to dustin
  • Status changed from new to assigned

comment:5 in reply to: ↑ 3 Changed 3 years ago by zoresvit

Replying to pedersen:

Thanks for the example! It does work with v0.9.0b5.

But not with v0.9.0b6. The form shows up empty with the following script error:

TypeError: Cannot read property 'type' of undefined
    at http://localhost:8080/scripts.js?_1453842444454:16:7953
    at post (http://localhost:8080/scripts.js?_1453842444454:12:4329)
    at http://localhost:8080/scripts.js?_1453842444454:4:25469
    at re (http://localhost:8080/scripts.js?_1453842444454:4:25526)
    at m (http://localhost:8080/scripts.js?_1453842444454:4:19511)
    at s (http://localhost:8080/scripts.js?_1453842444454:4:15620)
    at s (http://localhost:8080/scripts.js?_1453842444454:4:15643)
    at s (http://localhost:8080/scripts.js?_1453842444454:4:15643)
    at s (http://localhost:8080/scripts.js?_1453842444454:4:15643)
    at http://localhost:8080/scripts.js?_1453842444454:4:15061 <forcefield field="rootfield" class="ng-isolate-scope">

The reason I want v0.9.0b6 is because it introduced masterFQDN parameter for Docker Latent Builder which I want to use. Will try to solve it :)

comment:6 Changed 3 years ago by dustin

https://github.com/buildbot/buildbot/pull/1966 adds the first example. I'll need to look at why that didn't work with b6.

comment:7 Changed 3 years ago by tardyp

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.