tardyp changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-2.10.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | logs: https://freenode.irclog.whitequark.org/buildbot
jcarl43 has quit [Quit: WeeChat 3.0]
_whitelogger has joined #buildbot
infobob has quit [Excess Flood]
infobob has joined #buildbot
kraiskil has joined #buildbot
antranigv_ is now known as antranigv
kraiskil has quit [Ping timeout: 240 seconds]
kraiskil has joined #buildbot
dol-sen has quit [Remote host closed the connection]
dol-sen has joined #buildbot
chapipo has quit [Ping timeout: 260 seconds]
lohfu has quit [Ping timeout: 260 seconds]
chapipo has joined #buildbot
lohfu has joined #buildbot
medfly has joined #buildbot
<medfly> I am wondering if I should expect to be able to use the worker's numcpus in my BuildFactory, or do that as some shell invocation
kraiskil has quit [Ping timeout: 240 seconds]
kraiskil has joined #buildbot
andycooper has quit [Ping timeout: 260 seconds]
andycooper has joined #buildbot
medfly has quit [Read error: Connection reset by peer]
kkleine has joined #buildbot
<kkleine> Hi there. When I have installed buildbot on a machine I can call "buildbot try" to kick off a try build. But when I don't have that installed I wonder if there's a similar HTTP endpoint that I can POST to in order to kick off a try build?
<kkleine> The closest I can find is to have a force scheduler but I'm not sure that is what I want (http://docs.buildbot.net/current/developer/raml/forcescheduler.html#raction-/forceschedulers/{schedulername}%20(method=force)). Where exactly is the difference and capabilities between a force and a try build? I guess the try build allows for passing properties along at least.
<kkleine> LePhilousophe, you did help me last time. Do you have clue maybe? ^
<kkleine> I guess this is the documentation for kicking off a build using a force scheduler, right? http://docs.buildbot.net/current/developer/rest.html#controlling
kraiskil has quit [Ping timeout: 264 seconds]