On Aug 23, 2010, at 5:16 PM, András Murányi wrote:
2010/8/22 Hans-Christoph Steiner hans@at.or.at
On Aug 20, 2010, at 9:27 PM, András Murányi wrote:
2010/8/20 Hans-Christoph Steiner hans@at.or.at
Could you make a copy your id_rsa.pub, give all read perms, and put it into /home/pd on your zero machine? Then I'll set up the buildbot user with it.
.hc
you got it, thanks. don't know where the ssh error is coming from... you have authorization for root@blinky and hans@WIENER
Andras
I'm guessing sometimes the dyndns is a little behind. Ok, you're key should be in buildbot@128.238.56.50 and also in pddev@ in the PdLab machines.
I'm working on the master config... One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
I couldn't yet find a way to schedule in an anarcon-like manner, but i'll keep digging.
That machine is up all the time, so regular cron is fine.
Then the build sources/targets: one will be vanilla, which is in git, right? Or can i find it in SVN too? Buildbot seems to handle SVN more easily than git. The other is pdextended, is it true that it cannot be fetched with a one-liner, but we still need to get the 0.42 core and GEM separately? It will be a bit cumbersome to do this with buildbot (especially when detecting changes).
vanilla is in git. Pd-extended 0.42 can be fetched with a oneliner using svn, it is just that currently Gem is an svn:external. Oh wait, perhaps 'scripts' is still from trunk. I can fix that. I think the first thing that would be most valuable is setting up builds for individual libraries, so checking out from svn and building, so like
svn co https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/wind... cd windowing make make install make dist
Can buildbot handle making debian packages? That would be nice. I think that could be a oneliner.
.hc
----------------------------------------------------------------------------
kill your television
I'm working on the master config... One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
cool
I couldn't yet find a way to schedule in an anarcon-like manner, but i'll keep digging.
That machine is up all the time, so regular cron is fine.
it's about the uptime of slaves, and scheduling is handled by the buildbot master (internally). e.g. my box is up very irregularly, which a called a "latent slave" in buildbot world, and i'm yet to understand how to integrate it http://buildbot.net/buildbot/docs/current/Latent-Buildslaves.html http://www.codelord.net/2009/10/04/writing-a-buildbot-latent-build-slave/
Then the build sources/targets: one will be vanilla, which is in git, right? Or can i find it in SVN too? Buildbot seems to handle SVN more easily than git. The other is pdextended, is it true that it cannot be fetched with a one-liner, but we still need to get the 0.42 core and GEM separately? It will be a bit cumbersome to do this with buildbot (especially when detecting changes).
vanilla is in git. Pd-extended 0.42 can be fetched with a oneliner using svn, it is just that currently Gem is an svn:external. Oh wait, perhaps 'scripts' is still from trunk. I can fix that. I think the first thing that would be most valuable is setting up builds for individual libraries, so checking out from svn and building, so like
svn co https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/wind... cd windowing make make install make dist
ok, i'll test with single libraries (once i'm there), and will work it out as far as making a complete pd-extended. you could tell me then which sources we actually want to build at the end (and, eventually, you could also tell me what commands to use to build each source tree.)
Can buildbot handle making debian packages? That would be nice. I think that could be a oneliner.
it can attend "make package" or packaging by shell command, but only RPM creation is built in :(
Andras
I'm working on the master config...
One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
Andras
On Aug 23, 2010, at 10:20 PM, András Murányi wrote:
I'm working on the master config... One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
Andras
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
.hc
----------------------------------------------------------------------------
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler
2010/8/24 Hans-Christoph Steiner hans@at.or.at
On Aug 23, 2010, at 10:20 PM, András Murányi wrote:
I'm working on the master config...
One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
err, i cannot connect to port 10012, but guess what, buildbot is not bug-free... :) can we try the newest from http://sourceforge.net/projects/buildbot/files/buildbot/0.8.1/buildbot-0.8.1... goes with 'sudo python setup.py build' and then 'sudo python setup.py install' better to do 'sudo apt-get remove buildbot' before
Andras
On Aug 24, 2010, at 7:57 PM, András Murányi wrote:
2010/8/24 Hans-Christoph Steiner hans@at.or.at
On Aug 23, 2010, at 10:20 PM, András Murányi wrote:
I'm working on the master config... One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
err, i cannot connect to port 10012, but guess what, buildbot is not bug-free... :) can we try the newest from http://sourceforge.net/projects/buildbot/files/buildbot/0.8.1/buildbot-0.8.1... ? goes with 'sudo python setup.py build' and then 'sudo python setup.py install' better to do 'sudo apt-get remove buildbot' before
Andras
Managing builtbot from source is a lot more work that "apt-get upgrade". Since buildbot hasn't been upgrading to 0.8.x in Debian or Fedora yet, my guess is that buildbot 0.7.x works.
What are the problems that you are having?
.hc
----------------------------------------------------------------------------
Information wants to be free. -Stewart Brand
I'm working on the master config...
One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
err, i cannot connect to port 10012, but guess what, buildbot is not bug-free... :) can we try the newest from http://sourceforge.net/projects/buildbot/files/buildbot/0.8.1/buildbot-0.8.1... goes with 'sudo python setup.py build' and then 'sudo python setup.py install' better to do 'sudo apt-get remove buildbot' before
Andras
Managing builtbot from source is a lot more work that "apt-get upgrade". Since buildbot hasn't been upgrading to 0.8.x in Debian or Fedora yet, my guess is that buildbot 0.7.x works.
What are the problems that you are having?
I cannot connect with my slave nor with the debugclient (GUI app). Tried telnet, it times out. Now the master is shut down, if you have an idea about the network, you can start it up with 'buildbot start /var/lib/buildbot/pd-master"
Andras
On Aug 24, 2010, at 8:50 PM, András Murányi wrote:
I'm working on the master config... One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
err, i cannot connect to port 10012, but guess what, buildbot is not bug-free... :) can we try the newest from http://sourceforge.net/projects/buildbot/files/buildbot/0.8.1/buildbot-0.8.1... ? goes with 'sudo python setup.py build' and then 'sudo python setup.py install' better to do 'sudo apt-get remove buildbot' before
Andras
Managing builtbot from source is a lot more work that "apt-get upgrade". Since buildbot hasn't been upgrading to 0.8.x in Debian or Fedora yet, my guess is that buildbot 0.7.x works.
What are the problems that you are having?
I cannot connect with my slave nor with the debugclient (GUI app). Tried telnet, it times out. Now the master is shut down, if you have an idea about the network, you can start it up with 'buildbot start /var/lib/buildbot/pd-master"
Andras
It seems that port 10012 is blocked after all. I cannot reach it from my house, but I can reach it from localhost and from a machine that's on the same switch (128.238.56.55):
buildbot@debian-lenny-i386:~$ telnet localhost 10012 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. ??pb?none^]quit
pd@ubuntu-hardy-i386:~$ telnet 128.238.56.50 10012 Trying 128.238.56.50... Connected to 128.238.56.50. Escape character is '^]'. ??pb?none
Maybe try a different port?
.hc
----------------------------------------------------------------------------
"Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman
I'm working on the master config...
One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
err, i cannot connect to port 10012, but guess what, buildbot is not bug-free... :) can we try the newest from http://sourceforge.net/projects/buildbot/files/buildbot/0.8.1/buildbot-0.8.1... goes with 'sudo python setup.py build' and then 'sudo python setup.py install' better to do 'sudo apt-get remove buildbot' before
Andras
Managing builtbot from source is a lot more work that "apt-get upgrade". Since buildbot hasn't been upgrading to 0.8.x in Debian or Fedora yet, my guess is that buildbot 0.7.x works.
What are the problems that you are having?
I cannot connect with my slave nor with the debugclient (GUI app). Tried telnet, it times out. Now the master is shut down, if you have an idea about the network, you can start it up with 'buildbot start /var/lib/buildbot/pd-master"
Andras
It seems that port 10012 is blocked after all. I cannot reach it from my house, but I can reach it from localhost and from a machine that's on the same switch (128.238.56.55):
buildbot@debian-lenny-i386:~$ telnet localhost 10012 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. ??pb?none^]quit
pd@ubuntu-hardy-i386:~$ telnet 128.238.56.50 10012 Trying 128.238.56.50... Connected to 128.238.56.50. Escape character is '^]'. ??pb?none
Maybe try a different port?
.hc
yes! ports<10000 seem to work. so... (tada.wav) Vanilla builds alrite on one slave. Nest step would be uploading the file, this can be done internally, just tell me please which file or directory is the actual build? And... how do we make a package with the Vanilla source? Sorry I never built it myself. Some more questions that came up meanwhile: Shall we update or copy the source each time? (see http://buildbot.net/buildbot/docs/latest/Source-Checkout.html) Do we need --enable-jack to configure Vanilla (after autogen)?
Andras
On Aug 25, 2010, at 9:54 PM, András Murányi wrote:
I'm working on the master config... One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.
I think 8010 and 10012 are not filtered on that network.
So, we have an 'alpha version' of the master config up and running http://128.238.56.50:8010/ Tomorrow i'll shut it down (first i wish to see how the scheduler behaves) and continue configuring... need to give meaningful names to slaves, check scheduling, source access + change tracking and finally the actual build processes.
This is awesome! The RPM building could also be useful, since we don't have an RPM builder at the moment. It would be nice if people making Pd libraries could use this to make versions of their library for all the various platforms.
err, i cannot connect to port 10012, but guess what, buildbot is not bug-free... :) can we try the newest from http://sourceforge.net/projects/buildbot/files/buildbot/0.8.1/buildbot-0.8.1... ? goes with 'sudo python setup.py build' and then 'sudo python setup.py install' better to do 'sudo apt-get remove buildbot' before
Andras
Managing builtbot from source is a lot more work that "apt-get upgrade". Since buildbot hasn't been upgrading to 0.8.x in Debian or Fedora yet, my guess is that buildbot 0.7.x works.
What are the problems that you are having?
I cannot connect with my slave nor with the debugclient (GUI app). Tried telnet, it times out. Now the master is shut down, if you have an idea about the network, you can start it up with 'buildbot start /var/lib/buildbot/pd-master"
Andras
It seems that port 10012 is blocked after all. I cannot reach it from my house, but I can reach it from localhost and from a machine that's on the same switch (128.238.56.55):
buildbot@debian-lenny-i386:~$ telnet localhost 10012 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. ??pb?none^]quit
pd@ubuntu-hardy-i386:~$ telnet 128.238.56.50 10012 Trying 128.238.56.50... Connected to 128.238.56.50. Escape character is '^]'. ??pb?none
Maybe try a different port?
.hc
yes! ports<10000 seem to work. so... (tada.wav) Vanilla builds alrite on one slave. Nest step would be uploading the file, this can be done internally, just tell me please which file or directory is the actual build? And... how do we make a package with the Vanilla source? Sorry I never built it myself. Some more questions that came up meanwhile: Shall we update or copy the source each time? (see http://buildbot.net/buildbot/docs/latest/Source-Checkout.html) Do we need --enable-jack to configure Vanilla (after autogen)?
Andras
The way that this would be super useful is if buildbot builds after every commit to SVN or git. It looks like SVN polling support is built-in
http://buildbot.net/buildbot/docs/0.7.12/#SVNPoller
For git, it supports checkout, but there are some external scripts for polling:
http://buildbot.net/buildbot/docs/0.7.12/#Git http://stackoverflow.com/questions/645430/have-buildbot-poll-a-git-repositor... http://buildbot.net/trac/ticket/130
.hc
----------------------------------------------------------------------------
so... (tada.wav) Vanilla builds alrite on one slave. Nest step would be uploading the file, this can be done internally, just tell me please which file or directory is the actual build? And... how do we make a package with the Vanilla source? Sorry I never built it myself. Some more questions that came up meanwhile: Shall we update or copy the source each time? (see http://buildbot.net/buildbot/docs/latest/Source-Checkout.html) Do we need --enable-jack to configure Vanilla (after autogen)?
Andras
The way that this would be super useful is if buildbot builds after every commit to SVN or git. It looks like SVN polling support is built-in
http://buildbot.net/buildbot/docs/0.7.12/#SVNPoller
For git, it supports checkout, but there are some external scripts for polling:
http://buildbot.net/buildbot/docs/0.7.12/#Git
http://stackoverflow.com/questions/645430/have-buildbot-poll-a-git-repositor... http://buildbot.net/trac/ticket/130
.hc
yes, git is more cumbersome when it comes to polling, so i will work this out with daily builds and see the polling stuff after. the older buildbot version also has some limitations in this direction. can you help me with the other questions please? - is --enable-jack needed to configure Vanilla? - where do i find the Vanilla build when ready? - how do we make a package of Vanilla? - which mode shall the slaves use to checkout the source?
Andras
On Aug 26, 2010, at 12:55 PM, András Murányi wrote:
so... (tada.wav) Vanilla builds alrite on one slave. Nest step would be uploading the file, this can be done internally, just tell me please which file or directory is the actual build? And... how do we make a package with the Vanilla source? Sorry I never built it myself. Some more questions that came up meanwhile: Shall we update or copy the source each time? (see http://buildbot.net/buildbot/docs/latest/Source-Checkout.html) Do we need --enable-jack to configure Vanilla (after autogen)?
Andras
The way that this would be super useful is if buildbot builds after every commit to SVN or git. It looks like SVN polling support is built-in
http://buildbot.net/buildbot/docs/0.7.12/#SVNPoller
For git, it supports checkout, but there are some external scripts for polling:
http://buildbot.net/buildbot/docs/0.7.12/#Git http://stackoverflow.com/questions/645430/have-buildbot-poll-a-git-repositor... http://buildbot.net/trac/ticket/130
.hc
yes, git is more cumbersome when it comes to polling, so i will work this out with daily builds and see the polling stuff after. the older buildbot version also has some limitations in this direction.
I think we can start with SVN since that should be easier. If that works nicely, then we can struggle to get git polling working.
can you help me with the other questions please?
- is --enable-jack needed to configure Vanilla?
Not needed, but it would be good to have in the test builds to make sure it works.
- where do i find the Vanilla build when ready?
- how do we make a package of Vanilla?
We could do something like "make DESTDIR=/tmp install" and then run it from there for tests.
- which mode shall the slaves use to checkout the source?
I'm not sure what "mode" means in this context. Here's the git URL to use for pd-vanilla:
git://pure-data.git.sourceforge.net/gitroot/pure-data/pure-data
.hc
----------------------------------------------------------------------------
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." --Bjarne Stroustrup (creator of C++)