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
<LePhilousophe> it's not an error
<LePhilousophe> you can't provide the information because it isn't there
<LePhilousophe> what do you provide to the try scheduler? if it's not a github PR you can't push anything to it
<kkleine> LePhilousophe, let me ask differently. Who normally provides the information of repo_owner and repo_name? :)
<LePhilousophe> the sourcestamp
<kkleine> LePhilousophe, I didn't fully grok this concept.
<kkleine> LePhilousophe, project = sourcestamp['project']
<kkleine> repository = sourcestamp['repository'] seem to be relevant and so the question can be asked who is supposed to provide this information?
<LePhilousophe> when you have an build triggered, a sourcestamp is generated for the code checked out
<LePhilousophe> it contains various informations like repository, commit id, etc.
<kkleine> LePhilousophe, so that sounds like it is the scheduler's job?
<LePhilousophe> scheduler and change hook I think
<LePhilousophe> but what do you provide through the TryScheduler?
<LePhilousophe> I think that if you want to push to GitHub you must use a GitHubPullrequestPoller or sth like that
<kkleine> LePhilousophe, "but what do you provide through the TryScheduler?" you mean what properties I provide when calling "buildbot try --property=key=value?"
<LePhilousophe> yes
<kkleine> LePhilousophe, it looks as if this function of the Try Scheduler handles the repo and project, right? https://github.com/buildbot/buildbot/blob/e630745771/master/buildbot/schedulers/trysched.py#L128
<kkleine> One second for the params
<kkleine> I meant properties
<LePhilousophe> in fact the question is more: what do you try to achieve
<LePhilousophe> because if I understand correctly try scheduler, it's for patch provided through buildbot try command. It's not something which is in a Github PR
<kkleine> LePhilousophe, I try to kick off a build from "anywhere" using "buildbot try" and after the build was run or when it was kicked off have a message appear as a regular comment in a PR that is associated with it. I noticed that amongst my properties passed to buildbot try, there's no "project".
<LePhilousophe> you should use GitHubPullrequestPoller instead
<LePhilousophe> or the Github change hook
<LePhilousophe> maybe you can hack the thing by defining manually the missing properties
<LePhilousophe> and note that I am just a user of buildbot :)
<kkleine> LePhilousophe, my setup is quite exotic. We want to be able to build any PR on any try builder upon user request. I think the GitHubRequestPoller or Github Change Hook won't allow to react upon this. At the moment a try build is kicked off when I have a comment like "/must-build trybuiler0" in my PR. Strange setup I know.
jcarl43 has quit [Quit: WeeChat 3.0]
<kkleine> LePhilousophe, I have added the missing project and repository properties to the buildbot try call but the problem is still the same in buildbot
<kkleine> LePhilousophe, at the moment github cannot publically reach the buildbot server, which is why I have a self-hosted actions runner that federates the request to issue a try build when it sees a "/must-build-on trybuiler" comment.
<kkleine> I think this disqualifies the buildbot change hook setup.
<kkleine> LePhilousophe, but I still wonder if there's anything I can do to teach "teach" the GitHubCommentPush function which repo to push the comment to. Be it through buildbot try properties or some setting in the scheduler or so. No real user is calling the buildbot try command in our scenario. Instead we hide it behind a comment on a PR. This is to hide complexity of buildbot try but also to not expose it directly at all to anybody.
<kkleine> Will go to bed and try more on Monday. Happy Weekend and thanks for your help LePhilousophe .
kkleine has quit [Ping timeout: 268 seconds]
_whitelogger has joined #buildbot
ewong has quit [Ping timeout: 256 seconds]
ewong_ is now known as ewong
jcarl43 has joined #buildbot
jcarl43 has quit [Quit: WeeChat 3.0]
kraiskil has joined #buildbot
kraiskil has quit [Ping timeout: 256 seconds]
kraiskil has joined #buildbot
RP has joined #buildbot
kraiskil has quit [Ping timeout: 246 seconds]
kraiskil has joined #buildbot
kraiskil has quit [Ping timeout: 256 seconds]
dol-sen has quit [Remote host closed the connection]
dol-sen has joined #buildbot
<shurdeek> can I remove duplicate jobs? I have github hooks both for upstream and a fork. When I open a PR and then push to the branch, it runs every job twice: once because a branch in the fork was modified, and once because the PR was modified.
<shurdeek> this is an unnecessary waste of resources
kraiskil has joined #buildbot
kkleine has joined #buildbot
kraiskil has quit [Ping timeout: 246 seconds]
kraiskil has joined #buildbot
kkleine has quit [Ping timeout: 264 seconds]
medfly has joined #buildbot
kraiskil has quit [Ping timeout: 272 seconds]
alicef has quit [Quit: install gentoo]
alicef has joined #buildbot
kraiskil has joined #buildbot
skelly has joined #buildbot
medfly has left #buildbot [#buildbot]
rjarry has quit [Ping timeout: 256 seconds]
mirko has quit [Ping timeout: 256 seconds]
mirko has joined #buildbot
ngladitz has quit [Ping timeout: 256 seconds]
jotik_work has quit [Ping timeout: 256 seconds]
Benett has quit [Ping timeout: 256 seconds]
Benett has joined #buildbot
ngladitz has joined #buildbot
rjarry has joined #buildbot
kraiskil has quit [Ping timeout: 264 seconds]
kraiskil has joined #buildbot
kraiskil has quit [Ping timeout: 260 seconds]
kraiskil has joined #buildbot
kkleine has joined #buildbot
kraiskil has quit [Ping timeout: 256 seconds]
kkleine has quit [Ping timeout: 272 seconds]
kveremitz has joined #buildbot