On Aug 26, 2010, at 2:38 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
For git, it supports checkout, but there are some external scripts for polling:
.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.
Alrite. My box may fall out then, because i cannot handle so many build cycles per day, or i'll try to find a way to limit it to one build cycle on 'civilian' boxes like mine.
Ah yes, that makes sense. I was thinking the full time machines.
Or a Dell Zino for 250 USD, its 64-bit and runs Debian/Ubuntu nicely.
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?
? I know it's a dummy question, but i need to know so that i can test uploading the build.
you can look for pd/src/pd, that is where the pd binary is when its built but not installed.
- 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.
What kinds of tests do you imagine? Buildbot has support for unit tests and more.
Basically running pd patches that are designed to test something, then output a standard result, like the word "SUCCESS" or something like that. We need to write them :)
- which mode shall the slaves use to checkout the source?
I'm not sure what "mode" means in this context.
Andras