Hi Joe, Indeed, buildbot is designed to be a pretty generic task runner framework. It does not have to be triggered by source code change. The features you'll probably need are: authentication plugins: http://docs.buildbot.net/latest/manual/cfg-www.html#web-authentication Forcescheduler: http://docs.buildbot.net/latest/manual/cfg-schedulers.html#forcescheduler-scheduler
And you'll probably need a custom buildstep to output your results as a HtmlLog http://docs.buildbot.net/latest/developer/cls-buildsteps.html#buildstep Regards Pierre Le mar. 15 mars 2016 à 13:41, . <[email protected]> a écrit : > Hi, > I have some limited experience using Buildbot for automated testing, but > I am interested in the possibility of utilizing it for tracking > long-running machine learning tasks. > At first blush it seems like it would be a good fit for this sort of > task, particularly because of how easy it is to customize many aspects of > the build process. > > The idea is to use it as a platform to launch and track the training of > statistical models at work, then provide a nice summary of the results > (training/testing/regressions/comparisons) when they are prepared. > > I interested in starting with the latest version (still-beta?) of > Buildbot and am basically just curious if there are any other > users/developers out there that have some kind of experience (bad or good) > of using Buildbot for this sort of task (for which it was not explicitly > designed). > > Cheers! > > > > > _______________________________________________ > users mailing list > [email protected] > https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
