[Buildbot-devel] Is possible to have more than one server in git_buildbot.py?

[shiny knight]

Sorry, let me elaborate more.

i have a main repository; with Git; where we all commit. I have a main master buildbot with 2 slave, which build at different time and with different settings.

Now I need to add a second master, because our project is ready for specific tests. I could have a third slave, but these tests takes time, and I would prefer to run them on a separate master/slave system. Also to keep things separated, since they will run in slightly different environments, and my waterfall page is already too big as is, with all the builders that I have :)

The problem is related to the updates to the code: when someone commit; we have the git_buildbot.py that is called by the post hook on the Git server; but it send updates only to the main buildbot. The script has only one field where you put the server, does not accept multiple entry.

I want to add also the second master, so they both gets the commits and trigger builds. This also allow me to build in parallel on both systems.

I have considered to simply add a change to the hook, so when a change is made; it will send 2 calls to the git_buildbot.py, with different buildbot master names, passed as parameter. While in the python script, I add the parameter passed by the git hook, so in fact the procedure is done twice, for both master.

I am sure that there are other solutions; I was just trying to figure out if there is something already baked out there. Otherwise I am not too concerned to gets my hands dirty and make the changes on the git server :) I am still learning Python, but I think that should be moderately easy to implement such change.

I am open to different approach; all that I need is to have the notifications that a change has been made on the Git server, on 2 or more buildbot master; so I can trigger builds and keep track of changes.

Thanks

On Jan 7, 2014, at 12:25 PM, Pierre Tardy <tardyp at gmail.com> wrote:

> Hi Kica,
> Your question looks a bit confuse to me. I have the feeling that you are taking a fuzzy path.
> Could you perhaps explain your original problem, so that we can guide you on a appropriate approach that would be easy to implement with buildbot?
> 
> 
> Pierre
> 
> 
> On Mon, Jan 6, 2014 at 1:59 AM, shiny knight <theshinyknight at me.com> wrote:
> Hi all
> 
> I am checking the feasibility to have multiple master that perform different actions, but that uses the same repository.
> 
> I have one master configured, so I have the git_buildbot.py set for that server, on my git repo. Now I would like to add another master, which takes the same code from the same repository, but does different actions. I know that you may suggest to do all on one master, making different slaves, but it is not an approach that I can use.
> 
> So, since I was not able to find in the documentation the answer, I hope that you may clarify this for me.
> 
> When I select a server in the git_buildbot.py, I am forced to use only one, or may I add multiple server?
> 
> Could I simply replace the code, so instead of executing the functions on one entry, I may loop trough a list of entries? Or is something that goes against how the Buildbot was implemented?
> 
> All that I need, is to see the same revisions and commits on the second server, as I see them on the first one, so I can trigger the build.
> 
> I thought I would ask first, before touching the script and chase ghosts...maybe someone already did what I am trying to implement, so I don't have to re-invent the wheel.
> 
> Thanks
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20140107/738c07d9/attachment.html>