verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
<dol-sen> I thought there was one now. I made one for work years ago, it was suppose to be submitted, but never was. I was sure there was another added since...
<dol-sen> oh, yeah, it was based on the older system, not the newer reporter system...
dol-sen has quit [Ping timeout: 250 seconds]
dol-sen has joined #buildbot
moshevds has joined #buildbot
<moshevds> Hi. I have a change that I want to make to my team's buildbot instance. I thought I'd ask here first, in case someone has any pointers. We work trunk based, so it is rare for teammembers to commit on a new branch, but what does happen occasionally is that someone pushes multiple commits at once. When this happens, the console view shows the commits in the wrong order (because the timestamp is the same,
<moshevds> I guess). I imagine that the console view could be encouraged a bit more to sort them, but I'm not sure where to start looking for how this happens. Any ideas?
Guest34 has joined #buildbot
<Guest34> hi i try to start a build-run  "requests.post(host+"/api/v2/forceschedulers/Schedulername",json={"jsonrpc": "2.0", "method": "force", "id":1,  "params": {"myparam":"value"}})" it start but the "myparam" value dos not appear in the properties wht do i do wron here?
tgamblin has quit [Ping timeout: 248 seconds]
Guest34 has quit [Quit: Client closed]
Guest34 has joined #buildbot
Guest34 has quit [Quit: Client closed]