Hi Stefan, buildbot_travis is not dead, actually I use it for ~20 internal projects. Its maintained here, and work with buildbot nine: https://github.com/tardyp/buildbot_travis
Here is the step that takes care of dynamically creating the steps according to the config: https://github.com/tardyp/buildbot_travis/blob/master/buildbot_travis/steps/create_steps.py#L182 The idea is to get the yaml file from the worker in a step just after the source fetcher (the Git step) There is an api for that: http://docs.buildbot.net/latest/developer/cls-buildsteps.html#buildbot.process.buildstep.buildbot.process.buildstep.CommandMixin.getFileContentFromWorker and here is how it is used in buildbot_travis: https://github.com/tardyp/buildbot_travis/blob/master/buildbot_travis/steps/base.py#L50 HTH, Pierre Le mer. 27 avr. 2016 à 00:05, Stefan Seefeld <[email protected]> a écrit : > Hello, > > I'm trying to figure out whether it's possible for a buildbot instance > to fetch a project-specific build logic from the project's source tree, > rather than hard-coding it into the buildmaster's configuration. > > In fact, I'm setting up a buildbot instance for a project that's hosted > on github and which already uses travis-ci for some platforms. I very > much like the idea to keep the build logic in the project itself (e.g., > as .travis.yml), so I can update it with the rest of the code, without > having to reconfigure the CI infrastructure. > > Is anything like this possible with BuildBot ? > > (I just discovered https://github.com/isotoma/buildbot_travis, but it's > not clear to me how this works.) > > Thanks, > Stefan > > -- > > ...ich hab' noch einen Koffer in Berlin... > > _______________________________________________ > users mailing list > [email protected] > https://lists.buildbot.net/mailman/listinfo/users >
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
