Le mar. 18 oct. 2016 à 10:35, Tristram, Falk <falk.trist...@cognex.com> a écrit :
> Hi Pierre, > > > > it would be great if you could add an API warning, when someone tries to > actually use this function. > We can try to make something like this indeed. I'll give it a try. > > > Could you give me more details about the meaning of “purely static” in > this context. > It means that it cannot change after buildbot configuration. It is stored in the db as a json description of the forcescheduler configuration, so there is not python object or callback that can be used > I would prefer a solution that circumvents this problem by updating the > value on a time basis. > > This could be done by a “Poller” that updates the list of tags every five > minutes. > What you can do is to generate the list of choice during the configuration in your master.cfg. And you can add a external cronjob that does buildbot reconfig every now and then. > > > If I understand the implementation in 0.8.12 correctly, getChoices was > invoked when someone opened the ForceScheduler site. > > My requirement is simply that the list of tags is up-to-date, after a > short amount of time. > > > > Do you think, that time-based updates will work? > I think that could work indeed
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users